Mobile products,explained.

Everything we publish about the thing a customer carries in a pocket, including the cases where the honest answer is that they do not need one.

The questions a company asks before committing to an app, which is the most expensive decision on this list to get wrong.

Deciding whether to build something? The service page is the one to read. Reading around the subject? Stay here.

Published on this topic

Everything filed undermobile products.

The scope of this index

The test that separates a business that needs an app from one that needs a mobile website that actually works.
What an app costs in its second year, which is the year nobody budgets for and the one that decides the outcome.
What the two app stores require, and what their review cycles do to a release schedule planned around a launch date.
What has to be true before an app is worth building, stated as conditions rather than as enthusiasm.

The mobile website itself: Websites and Platforms.
The same job on a screen a customer already has: Web Applications and Portals.
Keeping it healthy after release: Ongoing support.

A post sits under exactly one topic. Nothing is cross filed, because a piece that appears in three places is a piece nobody can find a second time.

Where to go next

I know what I need to build.

A free conversation, then a written proposal with scope, price, and timing.

One process creates too much manual work.

We map it, then define what a connected system should do next.

My website is underperforming.

A written report and a prioritized plan of what to fix first.