Mobile app development for Norwegian businesses

Do you need an app at all?

An app costs more to build and maintain than a website, so start with the reason. Apps earn their place when people use the product often, need push notifications, work offline, use the camera or sensors, or sign in many times a week. A one-off enquiry or a brochure is better served by a fast mobile site.

If you are unsure, a progressive web app can be a cheaper first step. Our PWA vs native app comparison sets out the trade-offs. We say plainly when a website is enough.

Choosing the technology

We pick the lightest option that meets the need, then explain why. Code and store accounts are in your name.

Norwegian login, payment and language

Many Norwegian users expect to sign in with Vipps or BankID rather than a new password. Vipps Login suits consumer apps. BankID, normally through an identity broker, suits services that need strong identity checks, such as finance, health or public-facing portals. Each has onboarding steps and a cost that we confirm during scoping.

In-app payments are a separate topic. Digital goods sold inside an app usually fall under the store's own billing rules, while physical goods and services can use Vipps MobilePay or cards. We check the current store policy before designing the checkout.

The interface is written in bokmål, with English as an option. Text boxes must handle æ, ø and å, sorting should follow Norwegian order, and dates and currency use Norwegian formats. Nynorsk is a later addition if your audience needs it.

Privacy and accessibility

Norway applies the GDPR through the Personal Data Act, supervised by Datatilsynet. In an app, that means a clear privacy notice, a record of what data is collected and why, careful use of analytics and advertising SDKs, and a way for users to ask for access or deletion. App stores also require a data declaration, and we complete it from the data map.

Public-facing apps may fall under Norwegian universal design rules, which cover ICT solutions. We build with screen reader labels, scalable text, sufficient contrast and touch targets that are easy to hit, and test on real devices. Confirm with counsel whether your app is covered.

From first build to store release

1. Scope and prototypeKey screens and flows in a clickable prototype you can test with real users.
2. Build in sprintsA new installable build every week through TestFlight and Google Play internal testing.
3. Test on devicesOlder and newer iPhones and Android phones, poor networks and offline cases.
4. Submit and launchStore listings, screenshots, privacy forms and review handling, with accounts in your name.

Store review times vary and a rejection can add days, so we plan a buffer. Norway is 4 hours 30 minutes behind India in winter and 3 hours 30 minutes behind in summer, so weekly demos fit your morning.

Push notifications need care. They require permission on both platforms, and users who find them noisy switch them off or delete the app. We agree a short list of useful messages, such as order status or booking reminders, and give users control over each type.

Keeping the app healthy after launch

Phones and operating systems change every year. Apple and Google also raise requirements for new submissions, such as target versions and privacy declarations. An app left alone for twelve months can stop working well or be removed from a store.

We offer a monthly maintenance block for crash fixes, platform updates, dependency upgrades and small features. We also set up crash reporting from day one, so problems show up in a dashboard before they show up in reviews.

Pricing

Projects start at $1,500, and our rate is $30 an hour. The number of screens, integrations, back-end work and platforms decide the price. Our mobile app development service page describes the general process. If the app needs a server and dashboard, see web app development in Norway. A fixed quote follows a short call.