Apps and websites

From idea to the App Store, and kept running after.

I build apps and websites for founders, companies and the public sector. All the way, from the first sketch to the version people download, and I stay on after launch so it keeps working.

Apps
iPhone and Android from one codebase
Web
Websites, web apps and admin sites
Behind
Logins, payments, notifications and data
After
Kept running and developed

01 · Three starting points

Where are you today?

  • New build

    From sketch to launch

    From the first sketch to the version people download.

    • Clickable sketches before any code
    • A test version on your own phone early

    When you have an idea, even half of one.

  • Takeover

    An app that wobbles

    It works most days, until it does not.

    • I do not throw it away. It is made solid while it runs
    • Tests around money and access first

    When whoever built it has moved on.

  • Operations

    Further development

    Apps need care to keep working.

    • Updates when Apple and Google change their requirements
    • The next part is built when you are ready

    When the app is out, and should get better.

02 · How it works

You always know what is happening, and you can try it yourself.

  1. 01

    We talk

    You tell me what you want to achieve and who it is for. Half an idea is enough. I ask a lot of questions, and I tell you honestly what I would build first and what can wait.

  2. 02

    You get a sketch to react to

    Before any code, you get screens you can click through. Changing your mind on a sketch costs almost nothing. Changing it in a finished app does not.

  3. 03

    I build in small steps you can try

    You get a test version on your own phone early, and a new one each time something is ready. You try it, we adjust, and the end has no big surprises.

  4. 04

    We launch

    I handle the App Store and Google Play: the listing, the screenshots, the review and the release. For a website, the domain, hosting and making sure search engines can find it.

  5. 05

    I stay on

    Phones get a new operating system every year and apps need care to keep working. I keep it running, fix what breaks, and build the next part when you are ready for it.

03 · In depth · Under the surface

What holds the app up.

What people see is the buttons. What decides whether the app is good is underneath: that the right people see the right things, that the money adds up and that it can grow.

  • Who sees what

    Customers, staff, partners and administrators see the same data, but each only their part. The rules live on the server, not just on the screen.

  • Payments that add up

    Cards, invoices and subscriptions, also through the App Store and Google Play. Nothing counts as paid until the payment is confirmed, and a double tap never charges twice.

  • Signatures that hold

    Agreements signed with BankID and stored so there is always one clear version of what was agreed.

  • Talks to other systems

    Public registries, accounting, maps and whatever the company already uses. When the other side is down, it retries instead of losing something.

  • Just as fast with millions

    The database is planned for the size it will be in a few years, not the size it has on launch day.

  • Tested, locked and watched

    Whatever handles money and access is tested automatically. Errors are caught, so I usually know something is wrong before a customer does.

I also test the security of apps others have built

04 · In depth · Technology

Built with what fits the job.

  • Apps

    One app that works the same on iPhone and Android. Every feature is built once, so you are not paying for two apps. I mostly use React Native and Expo, and Flutter when that fits better.

  • Websites and web apps

    Pages that load fast and are easy to change. A web app can open straight from a link or a QR code. I mostly use React and Next.js, and Vue.

  • What is behind them

    Logins, payments, subscriptions, maps, notifications and where the data is kept. I build that part too, so the app and everything it talks to are made to fit together.

05 · Takeover

Do you have an app that already wobbles?

Nobody dares touch the payment code, everything gets slower each month, and whoever built it has moved on. That is a good place to start. I make it solid while it keeps running.

  1. 01

    See what is happening

    First an overview of errors and slowness, so we see what is actually going wrong instead of guessing.

  2. 02

    Secure what matters most

    Tests around whatever handles money and access, so nothing gets worse while we work.

  3. 03

    Fix what hurts most

    Security holes and the bugs customers notice, in that order.

  4. 04

    Rebuild piece by piece

    One part at a time, without starting over unless it really pays off.

Common questions about apps.

Do you build apps for both iPhone and Android?

Yes. I build one app that works on both, so you do not pay for two. Often a website or an admin site where you manage the content belongs with it.

What does it cost to build an app?

It depends on what the app should do and what it has to connect to. We often start with the smallest version that gives value, and build on it afterwards. After a first conversation you get a concrete proposal.

What happens after launch?

I stay on. Apps must be updated when Apple and Google change their requirements, and new wishes always appear once people start using it.

Can you take over an app someone else built?

Yes. I start by seeing what is actually happening in it, secure what matters most and improve it piece by piece, while it keeps running.

Tell me about your idea.

What you want to achieve and who it is for. Half an idea is enough. I reply within a day.