hano.pro

Context

Hano is a mobile app, and it needed somewhere other than a store listing to explain the product, show its price and hand people the download. hano.pro was written for that: the page itself answers what someone who has never opened the app asks — what does this do, what will it cost me, is my data safe.

The site ships in two languages, Turkish and English.

Approach

• Show it instead of describing it. The opening types a sentence and an entry appears; directly below it sits a 28-second recording taken from the app's own screen, split into four chapters. Nothing staged, nothing sped up.
• A source behind every claim. The "what we don't touch" section cites the Google Play data safety declaration; the behavioural science section cites three papers (Michie et al. 2009; Dew, Britt & Huston 2012; Thaler 1985) and the kakeibo method Hani Motoko developed in 1904.
• The price is not hidden. Three plans in one table; the monthly/yearly switch also works out the per-person figure, and the "no charge per member" line stands next to the number that backs it.
• Questions end on the page. A 14-question FAQ and nine guides, with support, privacy, terms and account deletion each on their own URL.

Technical

• Stack: A PHP 8 application with no framework and no database; no build step. Guide content is read from a single JSON file.
• Two languages, server-side: A ?lang= parameter picks the language, the choice persists in a cookie, and responses carry Vary: Cookie so an intermediate cache can't serve the wrong one. Canonical and hreflang (tr, en, x-default) on every page.
• The page carries its own weight: The 66 KB interface script lives inside the HTML — there is no separate application JavaScript. Fonts aside, first load is 8 requests and ~185 KB; the stylesheet is 48.5 KB at source, 11 KB compressed.
• The film downloads nothing until asked: the video loads only when the poster is tapped, with a separate recording for Turkish and English.
• Structured data: MobileApplication, Organization, WebSite and FAQPage by page type, plus a sitemap, robots.txt and llms.txt.
• Images: App screens are WebP with their dimensions declared; 24 icons live in a single inline SVG library.

Outcome

Fifteen URLs across two languages are live, and the site feeds the app's App Store and Google Play listings. Design, development and copy are all mine.