Guides
No Code Information Editorial Team
How to read an app report without vanity numbers
Count the route you cared about at launch. Ignore the chart that only shows that the app opened.
After the phone operating system changes
A new iOS or Android is the builder's packaging problem. Your problem is still the content and the store accounts.
When a link is enough
A QR code to a kept-up page beats an icon nobody updates. Install the app when people come back or you need a push.
What to test before you call it finished
One real route, on the phone you will actually hand to a visitor, after the app has been closed and opened again.
Push notifications that people do not mute
A push is a promise that something changed. One a week that is true beats three a day that are not.
Keep published facts from going stale
A new page does not retire the old one. Date the change and point readers at the current answer.
What “works offline” should mean
Cached pages, saved items, and a true offline workflow are three promises. Write the one you mean.
Sections a small organization actually needs
Most clubs, venues, and local guides can start with six sections. Extra sections are a later argument.
What belongs in a first-year app budget
The subscription is one line. Store fees, a domain, writing, and someone's time sit beside it.
A content app and a shop are different products
Articles, audio, and a map are a publishing job. A catalogue with checkout is a retail job. The plans are rarely the same.