Skip to content
No Code Information App decisions, without a codebase Start here

For clubs, shops, and local publishers

Decide what the app has to do before you pick a builder.

Short guides for a mobile app, a web app, or both, without hiring someone to maintain a codebase.

Read the first guide Browse topics

Topics

Five areas. Pick the decision you are actually making.

Builders What the tool is for Compare plans after the brief is written. Product Offline, push, content Name the job the app still has to do. Publishing Stores and plain links Ship a link first. Add an icon when it earns one. Costs The first year of bills Price the stores, the writing, and the editor. Upkeep After the launch week Keep facts current once the phones update.

Recent guides

Practical notes you can use before a trial or a store submission.

Upkeep

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.

 Upkeep

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.

 Publishing

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.

 Publishing

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.

 Product

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.

 Upkeep

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.

Independent notes, not a vendor pitch.

We do not build the app, and we do not rank builders. The guides are here so you can write the brief, count the cost, and test one real route.

About this site