Common Misconceptions About App Development

App development is wrapped in folklore — most of it inherited from a decade ago when the field was much harder. Some of the most common assumptions cost small businesses real money and stop them building things that would genuinely transform how they operate. Worth airing them.

Misconception 1 — "It needs to be in the App Store"

For most small business apps, the App Store is the wrong distribution model entirely. Internal apps and customer portals work as web apps — accessible via a normal URL, no install friction, no Apple/Google review delays, no store fees. Modern web apps look and feel like native apps. The App Store should be a deliberate choice, not a default.

Misconception 2 — "We need iOS, Android, and web — three apps"

Almost never true today. A modern progressive web app or React Native build covers all three platforms from one codebase. The "three apps" assumption inflates budgets by 200% for no real benefit. Ask any developer suggesting three separate codebases why before agreeing.

Misconception 3 — "We have to build everything at once"

The opposite is true. Building everything at once produces a bloated v1 that nobody uses correctly. The fastest path to a working app is shipping the smallest useful version (8-12 weeks), watching how it's actually used, and adding features in priority order over the following year.

Case in pointSerinFlow

The operating system fundraising consultants didn't know they were allowed to want.

SerinFlow is a custom-built consultancy platform for fundraising consultants, bid writers and charity advisors. One place to manage relationships, opportunities, applications, delivery, reporting, invoices and AI consultancy intelligence — instead of seven disconnected tools.

Read the case study

Misconception 4 — "It'll be done in 3 months, then we're sorted"

Apps are not done; they're maintained. The 3-month build is just the start. Plan for an ongoing improvement cadence — small features quarterly, security/dependency upkeep monthly, occasional larger upgrades yearly. Apps that aren't maintained slowly degrade until they need a costly rebuild.

Misconception 5 — "We can use no-code and skip developers entirely"

No-code is brilliant for prototypes and lightweight internal tools. It hits a wall fast for anything that needs custom logic, performance, security, or integration. Many businesses build the v1 in no-code, validate the workflow, and then re-build properly once the requirements are clear. That's a sensible sequence — but pretending no-code scales infinitely is expensive.

Misconception 6 — "It costs £100k+ to build anything serious"

That's true for some genuinely complex enterprise apps. It's not true for the vast majority of useful small business apps, which usually land in the £15k-£40k range for v1, with a clear path to extend. The high-cost folklore puts owners off projects that would have paid for themselves in eighteen months.

Misconception 7 — "Off-the-shelf is always cheaper"

Cheaper this month, often more expensive over three years once you factor in seat licences, integration costs, workaround time, and missed-fit margin loss. Run the 36-month TCO honestly before defaulting to off-the-shelf. The maths often surprises.

For the underlying question, see does your business actually need an app?