This was supposed to end at Build 83

Honestly, we were not planning anything dramatic. The job was simple: fix the memory blow-up in Build 82, bump it to 83, call it a day.

Then curiosity showed up. Again. “What if an LLM could make search terms more accurate?” Innocent question. Famous last words. To stop the LLM from getting a little too creative, we tried a hidden-card rule: if the word can be translated, treat it as a real candidate. That experiment led us to VLM tests, and the small update started growing legs.

So the update that was meant to end at 83 kept running until GoPic 2.0.1, Build 120. There were stretches of roughly five hours of sleep and an unreasonable amount of focus. Now it is finally time to throw the doors open on the upgraded GoPic. Wiiiide open.

Android

  • Redesigned the OCR path around V6 preprocessing/detection and language-specific recognition, reducing redundant passes and improving memory use and OCR stability.
  • Refined the camera guide and language-selection flow, and made the path from camera or gallery image to search results smoother.
  • Stabilized Google sign-in, post-login return, My Page navigation, and session handling.
  • Refined rewarded-ad preparation/display timing and the free-scan credit flow to reduce awkward screen-transition timing.

iOS

  • Refined language-specific V6/V5 hybrid OCR routing and memory management to improve sign-recognition stability across different writing systems.
  • Improved the camera guide, language selection, and photo-import flow from capture through search.
  • Strengthened login return and session handling for more reliable account state and navigation.
  • Stabilized Premium purchase/restore and rewarded-ad preparation and display.

General improvements

  • Reworked key UI copy across 26 languages and aligned Android and iOS behavior more closely.
  • Improved location-aware search and the flow back to GoPic after viewing search results.
  • Fixed a long list of issues and improved memory use, screen transitions, overall performance, and stability.

A note from the dev team

We thought 83 would be the finish line. We made it to 120. Next time we will keep the update nice and quiet. Probably.