You Have an App Idea. Now What?
Most app ideas die as ideas. Not because they're bad, but because the road from idea to finished app seems impossibly long. It doesn't have to be.
Here are the steps. Concrete and without fluff.
Step 1: Validate Your Idea
Before you spend a single dollar, find out if anyone actually wants your app. Most people skip this step. It's the most common mistake.
How to do it: Talk to 10 potential users. Not friends and family. Real people in your target audience. Ask three questions:
- Do you have this problem?
- How do you solve it today?
- Would you pay for a better solution?
If 7 out of 10 say yes, you're onto something. If 3 out of 10 say yes, go back and adjust the idea. This week of talking can save you tens of thousands in wasted development.
Step 2: Make a Simple Sketch
You don't need Figma. You don't need design tools. You need paper and a pencil.
Draw the 5-7 most important screens in the app. Home screen. Registration. Main feature. Settings. That's enough.
The point isn't to make something pretty. The point is to think through the flow. What happens when the user opens the app? What's the first thing they see? How many taps does it take to complete the most important task?
Fewer taps is better. Always.
Web app or native app?
Before you choose between iOS and Android, ask yourself a different question: do you need a native app at all? A web app, also called a PWA, is a website that behaves like an app. The user adds it to the home screen and gets an icon, its own launch screen and full screen without a browser bar.
It is the simplest way into the app world, and for many businesses it is the right first choice.
What a web app can do:
- Install to the home screen. On Android the user gets an install prompt. On iPhone it is done manually through the Share menu and "Add to Home Screen". From iOS 26, those shortcuts open as their own app by default.
- Work without a connection. Content and data are cached on the device, so the app keeps working when coverage drops.
- Send push notifications. On Android this has worked for years. On iPhone it works from iOS 16.4, but only once the user has actually added the app to the home screen. An ordinary Safari tab cannot send notifications.
- Run everywhere. One codebase covers iPhone, Android, tablet and desktop. You maintain one product, not three.
Why it is often the right first choice:
- No app store to wait for. You skip Apple's review rounds and Google's checks, and you do not risk a rejection over formalities right before launch.
- Updates ship immediately. You publish, and everyone has the new version the next time they open the app. Nobody waits for users to update.
- No store commission on digital sales. If you sell digital content or subscriptions through an app in the store, Apple and Google take between 15 and 30 percent. The rates are changing, and Google cut its own in parts of Europe in the summer of 2026. If you sell nothing digital inside the app, the commission never applies anyway.
- Lower cost. One product to build and maintain instead of two, and no submission rounds to plan around.
What it cannot do: heavy graphics and 3D run slower than native. Advanced camera use, sensors, Bluetooth and NFC are limited, especially on iPhone. There is no background execution in the same sense. Widgets, watch apps and deep operating system integration are out. And it is not in the App Store, which matters if your customers look for you there.
Choose native when: the app needs heavy graphics or game-like performance, it depends on advanced camera or sensor use, or being present in the App Store and Google Play is a requirement.
We do not put a fixed price on a web app. Scope decides, but it typically lands below a native app, because there is one product to build and maintain instead of two.
Step 3: Choose a platform
If you have landed on native, the next question is iOS or Android. Or both? The answer for most people: start with iOS.
Why? iPhone users pay more for apps. The App Store has stricter quality standards, which forces you to build something good. And it's cheaper to start with one platform than two.
Android can come later. Once you know the concept works and you have paying users.
Exception: If your target audience is 80% Android users (e.g., delivery drivers or construction workers), start there.
Step 4: Find a Developer or Do It Yourself
You have three options:
- Developer/agency. Someone else builds the app. You manage the project. Costs more, but you get professional quality.
- No-code tools. Platforms like FlutterFlow or Adalo let you build simple apps without code. Limited design and functionality.
- AI-assisted development. With tools like Cursor or Claude, you can build the app yourself, even without much programming experience. AI writes most of the code. You steer the direction.
The last option has exploded in 2026. People without technical backgrounds are building working apps. It's not easy, but it's possible.
Step 5: Design and Prototype
Now you take the sketches from step 2 and turn them into a real design. A developer or designer creates mockups that look like the finished app.
A prototype is a clickable version you can test on your phone. No code yet. Just images you can tap through.
Test the prototype with 5 people. Watch where they get confused. Fix it. Test again. This round saves you from expensive changes during development.
Step 6: Development
Now the app gets built. How long does it take?
- Simple app (5-10 screens, basic functionality): 2-4 weeks.
- Standard app (10-20 screens, user profiles, payment solution): 4-8 weeks.
- Complex app (many integrations, real-time data, advanced functionality): 8-16 weeks.
AI has significantly cut development time. What took 12 weeks two years ago now takes 4-6 weeks. The quality is the same. The price is lower.
Step 7: Testing
The app needs to be tested on real devices. Different iPhone models, different screen sizes, different iOS versions.
Use TestFlight (Apple's testing tool) to send the app to 10-20 test users. Let them use it for a week. Collect feedback. Fix the bugs.
Apps that skip proper testing get bad reviews. Bad reviews kill apps. Don't skip this step.
Step 8: App Store Submission
Apple reviews your app manually. They check that it works, follows the guidelines, and doesn't crash.
Review typically takes 1-3 days. Sometimes faster. Sometimes they request changes, and you need to resubmit.
You need an Apple Developer account. It costs $99 per year. That's the only fixed cost for having an app in the App Store.
What does it cost in total?
A native app sits roughly between NOK 30,000 and 100,000. We agree the price case by case, once we know what the app actually has to do. A web app typically lands lower. Here is how the work spreads across that range for native:
- Lower end: 5-10 screens with basic functionality and no backend of its own.
- Middle: user profiles, payments, push notifications and a backend keeping data in sync.
- Upper end: real-time data, several integrations and multilingual content.
AI has driven prices down by 30-50% compared to 2024. It's cheaper than ever to build an app.
After Launch: What Then?
Many think the job is done when the app is in the App Store. It has only just begun. An app needs maintenance, updates, and marketing.
Apple releases new iOS versions every year. Your app needs to be updated to work with them. Users send feedback and bug reports. New features are needed to retain users.
Budget 10-20% of the development cost per year for maintenance. A NOK 50,000 app needs roughly NOK 5,000-10,000 annually in updates.
Common Mistakes to Avoid
- Too many features in version 1. Launch with the essentials. Add the rest based on what users actually ask for.
- Ignoring the App Store listing. Screenshots and copy in the App Store are your marketing. Spend time on them.
- No marketing plan. The app won't sell itself. Have a plan for how to reach your users.
Ready to Get Started?
Get in touch for a no-obligation conversation about how we can help you go from idea to App Store.