App, not a buzzword
"How much does an app cost?" sounds like one question. It is really about scope, platforms, and whether you need the App Store at all.
Almost every first call with a business that wants an "app" starts the same way: they want a number. The vendor wants to close. Then you discover that "app" meant three different products - a store listing on iOS and Android, an ops system with push, or a website that just works well on a phone.
I am Naor from NaorX. I do not sell a shelf price list, because every build is different - complexity, features, integrations, UI, and maintenance. What this article can do is explain what actually drives cost, where people burn money, and when a website or PWA does the job without store submission. If you read what builds WhatsApp bot pricing - same mindset, different product.
First: which "app" are we talking about?
Without that definition, every quote is a guess. In the market you will hear multi-x gaps for the same sentence in a brief - not always because someone is dishonest, because each side imagined a different product.
1) Native (iOS / Android in the stores)
Installed from a store, with icons, push, and deeper hardware access. Makes sense when you need store presence, heavy performance, or a daily-use product. Cost rises because you face two platforms (or a stack that covers both), review processes, and ongoing OS updates.
2) Cross-platform (Flutter / React Native and similar)
Shared UI for most screens, with platform-specific edges. Saves time versus two fully separate native apps, but it is not "half price by default." You still need real-device testing, store releases, and careful work around camera, payments, and background tasks.
3) PWA / website that feels like an app
A modern site you can install to the home screen, with partial offline, some notification options, and solid speed. No App Store. For many Israeli businesses this is the right answer - especially when customers arrive from WhatsApp, Google, or a link, not from browsing the store.
4) An "app" that is really a web system + mobile
Admin, customers, orders, reports - the phone is just how users touch it. The real question is the system, not the icon. I also cover tech choice in fullstack and polyglot development.
The question that saves months:
Do customers must find you in the App Store, or do they need something that works fast on a phone and connects to the business? Most SMBs need the second.
What actually builds the price (no shelf menu)
When I prepare a quote at NaorX, I do not invent a round number. Pricing comes from technical and business parameters - the same ones you should demand from any vendor:
- Screens and flows: login, profile, lists, pay, alerts, admin. Each screen is design + logic + QA.
- Backend: users, orders, files, roles. Without a solid server you have a pretty demo, not a product.
- Integrations: payments, SMS, WhatsApp, CRM, inventory, invoicing. Each connection is a mini-project - see the integrations guide.
- UI/UX: generic template versus a flow designed for your brand and process.
- Platforms: iOS only, Android only, both, or web/PWA.
- Security and roles: OTP, API protection, logs. Cheap to skip - expensive after an incident.
- QA and launch: real devices, store reviews, OS versions, failure paths.
- After launch: bugs, OS updates, small changes. Without that you bought a go-live, not a product.
How I handle price:
I do not publish a fixed "app price," because it is not a shelf SKU. In a free initial consult we break down what is needed for phase 1 versus later. Then you get a detailed quote - not one mysterious line. Same principle as the FAQ on the site.
Where people burn money
- "iOS and Android from day one" before the product is proven. Sometimes one market - or a PWA - is enough until usage is real.
- "Would be cool" features before the business core: chat, gamification, social feed - while a simple order flow still fails.
- Designing screens with no backend. You get a shiny demo that collapses on first real user.
- Choosing native because "everyone has an app." If traffic comes from Google and WhatsApp, a fast site with a clear CTA beats an empty store icon.
- A cheap quote with no written scope. Same red flags as in how to choose a developer in 2026.
When a website / PWA is enough (often)
If any of these fit, pause before signing for store apps:
- The user needs to order, pay, book, or contact - not live inside a product for an hour.
- Most traffic comes from search, ads, or WhatsApp - not store discovery.
- You need weekly process changes without waiting on Apple review.
- Budget and time need something working in the next months, not a 2028 vision deck.
A good PWA gives home-screen install, app-like feel, instant updates, and a link you can send. It does not replace every native case - but it saves many businesses from a heavy project too early.
Native vs cross vs PWA - a plain decision table
| Need | Native | Cross | PWA / web |
|---|---|---|---|
| Must be in the stores | Strong | Strong | No |
| Time to first usable version | Longer | Medium | Usually faster |
| Updates without store review | Limited | Limited | Immediate |
| Deep hardware / background access | Strongest | Good | Browser-limited |
| Fit for most local SMBs | Sometimes | Sometimes | Usually yes |
Ask this before you sign (client checklist)
- Screen list and one end-to-end flow (not "an app like Instagram").
- Stores required, or mobile web / PWA only.
- Who owns Apple / Google / server / domain accounts.
- What is included after launch: bugs, OS updates, small copy changes.
- Where the code lives and who owns it - also covered in what you get at project handover.
- Phase 1 plan versus "everything inside." A working product beats a deck.
Summary
"How much does an app cost" is a question about what you are building, not a magic menu. Native, cross-platform, PWA, and web systems are different paths with different cost, time, and risk. Most businesses in Israel do not need the heaviest path on day one. They need a product that closes a business flow on a phone.
Before you decide - start with "what must the user finish in three minutes." Then pick the stack. Only then talk about a detailed quote.
Got an "app" idea and not sure if it is a site, PWA, or store build?
At NaorX I help break it into a sane phase 1 - no generic shelf price. Describe the idea via the contact form, and we can see what should be built first.
Need help with your project?
Whether it's a website, bot, automation or something else - I'm here to help you build a solution that works
