App development: how we build apps with our clients
We build apps close to the people who'll use them, from idea to launch. This is how we work, and why our apps are still in use years later.
Most people think an app starts with a requirements document. With us it usually starts with a conversation, and a few days later you have a rough prototype in your hand. When you see something real early, you make better calls: we don't need that button, I'd pay for this, something's missing here.
From idea to something you can hold
We prefer to build a working prototype before we build the real app. Shorewalk, a guide app for cruise tourists in Kristiansand, went from an idea in the morning to an app on TestFlight that evening. It wasn't finished, but it was enough for people to try it and have an opinion.
If the prototype kills a bad idea, it has done its job. You'll know after a day, not after three months and a big invoice.
Apps that stay in use for years
An internal scheduling and job-management system we built for a construction company has been in daily use since 2018. Mine Gavekort, the gift-card app we built for our client iGive AS, is on the App Store and Google Play and used across Norway and Sweden.
The real test is whether an app still does its job five years on. That takes someone to run it, update it and fix things when they creak. We do that.
How we work together
MaartenTracker replaced a spreadsheet that had grown unmanageable for a passenger boat in the Kristiansand archipelago. It handles trip planning, crew and automatic customer notifications. We built it close to the people who use it, adjusting as we went instead of guessing up front.
You don't need to know anything about code, just what the app should do. We handle development, launch on the App Store and Google Play, and running it afterwards.
Have an idea for an app?
Tell us what you want the app to do, and we'll suggest the simplest way to get there. Get in touch, or see the projects we've built.