Web app development for Norwegian businesses

When a web app beats a website or a spreadsheet

A web app makes sense when people log in, data changes, or several roles see different things. Examples we are asked for in Norway include a client portal for a consultancy, a booking and resource tool for a service firm, a dashboard that merges data from several systems, and a quoting tool for a manufacturer.

If your process lives in a shared spreadsheet that three people edit and nobody trusts, an app with clear roles and an audit trail is usually the answer. If it is a handful of static pages, a website is cheaper. We tell you which is which.

A short discovery phase often saves more than it costs. In one or two workshops we map the roles, the data and the first release, and we list what the app should not do yet. A tight first scope is the most reliable way to keep a custom build on budget.

Norwegian building blocks

Our web app development page explains the general approach, and the cost guide shows what drives price.

Privacy by design

An app stores personal data by definition. Norway applies the GDPR through the Personal Data Act, and Datatilsynet expects privacy to be designed in, not added later. In practice we start from a data map: what the app stores, why, who can see it, how long it is kept and how a person can ask for access or deletion.

We build role-based access, audit logs, encrypted storage and export or delete functions into the first release. Hosting is chosen in an EU or EEA region where possible. Access by our team in India happens under a data processing agreement with transfer safeguards, using test data in development. Your lawyer should review the final setup.

Security and hosting

We apply the basics consistently: hashed passwords or federated login, least-privilege roles, input validation, dependency updates and encrypted backups. Secrets live in environment stores, not in code. Before launch we run a review against common web risks and fix what it finds.

Hosting is chosen with you. A managed platform in an EU or EEA region keeps operations simple, while a larger customer may require its own cloud account. Either way, monitoring and alerts are set up so that errors reach a person before they reach your customers.

Accessibility for apps

Universal design rules in Norway cover ICT solutions aimed at the public, which can include customer portals. We build forms with proper labels, readable error messages, focus management and keyboard paths, and test with a screen reader. Our target is WCAG 2.2 level AA. Confirm with counsel whether your app falls under the regulation.

For apps sold to others, rather than used inside one company, our SaaS development service covers multi-tenant design and billing.

How we build

1. ScopeUser roles, key screens and data are written down in a short specification you approve.
2. Thin first releaseThe smallest version that people can actually use, shipped in weeks, not months.
3. Weekly demosEvery week you click through the latest build on staging and change priorities.
4. Harden and hand overTests, monitoring, backups, documentation and ownership of all accounts.

We work in the Norwegian morning, which is the Indian afternoon. Norway trails India by 4 hours 30 minutes in winter and 3 hours 30 minutes in summer. For a larger product, the MVP development service shows how we phase a build.

Pricing

Projects start at $1,500, and our rate is $30 an hour. Number of roles, integrations, reports and the level of testing drive the price. You get a fixed quote within one working day of a short call, with the scope written out so changes are agreed before work starts. Code, repositories and cloud accounts are in your name from the first day.