akifumi

Most image tools ask for an upload first. Work screenshots, assets that aren't public yet, personal photos. I wouldn't put those on a server I don't control.

So GAZO Hub runs in the browser, with Canvas and WebAssembly. Image files don't go to a server. Offline use is a side effect of that, not a slogan. It also means I can't process them on my side. Fine. I'd rather not see them.

On client work I stayed in frontend for a long time. On my own products I do the planning, the code, the design, the release, and the fixes after. Not everything ships well. On note I've written about web apps that nobody used.

I've travelled every year for more than a decade, including a trip around the world. Over 40 countries and 100 cities. Confusing ATM fees and exchange rates are why I built NomadCalc and Travel ATM Cost. Travel stories are not the source of the numbers. Fees come from official tables. Local screens are for explaining the flow.

App Store and Chrome Web Store size specs are taken from official docs, with a review date. When a spec changes, I update that page. Size pages get a pass every quarter (January, April, July, October). Test numbers get remeasured when the tool changes.

If you find an error, use the contact form. I check the fact, fix the page, and keep it in the changelog. Bigger corrections get a note at the top. I don't write estimates as if they were confirmed.