NOEN
Let's talk
Web designMotion, identity and experiences that work on every screen size. Web developmentFast websites, integrations and workflows that fit together. HostingFrom HTTPS and file serving to CDN, recovery and scalable setups. AI & automationKnowledge assistants, document flow and conversations with clear control.
Back to home

02 / WEB DEVELOPMENT

More than pages.
Digital tools.

From a quick presentation page to a customer portal: we choose the architecture to fit the task. It should be simple for the user, even when a lot happens behind the interface.

This website is static files with a little JavaScript, with no framework that is not needed.

InterfaceAPIData

Shaped by possibilities

Choose an example

Example 01 / 03

Send what the user needs. When it is needed.

Static generation, server rendering and code splitting are different tools for getting content on screen quickly. None of them is right for every page.

Practical example

A campaign page with the same content for everyone can be delivered as finished files. A personal customer portal, on the other hand, needs sign-in and server logic. We can combine a light public part with a more advanced part where the task requires it.

How it can be used

A hotel can show rooms, images and location without waiting for the booking system. Available dates and prices are fetched when the guest opens the booking. The whole front page then does not depend on one external service.

What we aim for

Less unnecessary work in the browser and better control of perceived speed.

Static generationCode splittingLazy loading

Example 02 / 03

One service talks to the next.

Websites fetch and send data to payment solutions, booking systems, accounting and customer registers. We build integrations that tolerate failure and are easy to follow up.

Practical example

A form sends an enquiry both to email and to the customer system. If one fails, the message is queued instead of being lost.

How it can be used

A web shop synchronises stock status with an external system, with logging that shows what happened and when.

What we aim for

Integrations that run quietly day to day, and are clear when something needs fixing.

APIWebhooksLogging

Example 03 / 03

The browser can do more than you think.

With installable web apps, notifications and support for poor coverage, a website can behave like an app, without the user going through an app store.

Practical example

A member portal can be added to the home screen and opened directly, with the sign-in kept.

How it can be used

An event gives participants the programme in a way that also works when the network is poor.

What we aim for

An experience that is fast and familiar, without the cost of maintaining several apps.

PWAService workerOffline

Experience the technology

Follow a request.

See the connections behind the page.

  1. 01Browser
  2. 02API
  3. 03Data source
  4. 04Response

You open a service in the interface.

GET /service

A visual walk-through. No external request or order is sent.

What does this mean for your project?

Performance has to be measured on real devices and connections. We do not promise a specific score without having measured the actual solution.

Source: MDN: Lazy loading

More solutions

01Web designMotion, identity and experiences that work on every screen size.Explore 03HostingFrom HTTPS and file serving to CDN, recovery and scalable setups.Explore 04AI & automationKnowledge assistants, document flow and conversations with clear control.Explore

Have a task
we should look at?

Let's find a good solution

Let's talk

Tell us what you want to build.

The form is the quickest way. You get a reply from a person, and we start with a short conversation about the goal, not with a price list.

Email

hi@••••.no

Phone

+47 •• •• •• ••

Shown only after a tap and a short security check, so the address does not end up on spam lists.

What is it about?

We only use your details to reply to you.

Let's talk

Tell us what you want to build. You get a reply from a person.