Skip to content

Make your app improve itself.

A request in plain language. A tested build on your phone.

7+ years · 10+ apps shipped · Based in Sweden
A test build on your phone
Gymply on an iPhone, Tuesday’s home screen with today’s workout and meals, under a TestFlight notice: build 295 is ready to test, done workouts survive a reinstall
Alvar Aronija, triplefiveBook a 20-min intro callSchedule now

The way app development should have worked in the first place.

Ask

Your team says what to fix or build, in the tools you already use.

Build

The workflow makes the change, runs the tests and the code review.

Bug fixesCrash fixesCopy changesNew screensStore rejectionsPush notifications

Try

A build lands on your phone. You approve it, then it ships.

triplefive is run by Alvar Aronija, a senior mobile engineer. He built the workflow for Gymply, his own app, and it still runs there. When you write in, he is the one who answers, and every release goes out with his review.

It’s “no developer to chase” better.

One fixed price instead of a hire or an agency.

Builds on your phone

Every change arrives as a test build with a note.

An engineer signs every release

Read before it’s built, tried before it ships.

Any React Native app, any state

Bare or Expo, any version, with or without tests.

One real fix, start to finish.

A bug on Gymply, triplefive’s own app, October 2026. The report, the fix and the release are real; the build steps and the clock show a typical day.

  1. 0:00 elapsed

    The report

    A tester sends feedback from TestFlight, with one screenshot. That is the whole brief.

    “I have already completed the workout of the day, but after deleting the app and reinstalling it shows that I have not”
    Your team2 min · the workflow reads the screenshot and the code
  2. 0:02 elapsed

    The diagnosis

    Nothing was lost. The logged session and the green marks on the week strip come from the server; only the “done today” marker lived on the phone. Five files named, one decision flagged for the fix.

    The AI workflow1 h · until the engineer reads it
  3. 1:02 elapsed

    The go-ahead

    Reads the diagnosis and approves the fix. One label on the report, nothing else to write.

    The engineer9 min · the workflow writes the fix and the test
  4. 1:11 elapsed

    The change

    A pull request is open. The synced session now stands in for the missing marker. A new test fails on the old code and passes on the new. 844 tests pass; the two that fail were failing before and touch nothing in the change.

    The AI workflow5 min · automated code review reads the change
  5. 1:16 elapsed

    The checks

    Automated code review reads the change and passes it. The engineer asks for a test build with one comment.

    The AI workflow20 min · the build is signed and uploaded
  6. 1:36 elapsed

    The build

    A TestFlight build lands, made from the exact code in the pull request, with a note on what to check.

    The AI workflow30 min · until you open it on a phone
  7. 2:06 elapsed

    The phone

    You delete the app, reinstall the build, and the workout is still marked done. The one check the workflow could not make. You say it works.

    Your teamsame day · the engineer merges it when the day’s fixes are in
  8. end of day

    The merge

    The engineer merges the fix into dev. Overnight, the nightly build ships dev to TestFlight with a changelog of what merged, so the testers wake up to the fix.

    The engineerdays later · until the engineer decides the next release is ready
  9. release day

    The release

    The engineer pushes a version tag. Twenty minutes later the workflow has built it, attached the release notes in English and Swedish and submitted the build to Apple for review, set to roll out in stages once approved. Four decisions from a person: approve, try, merge, release. Everything else was the workflow.

    The engineer

About two hours from report to a build on a phone, of which the workflow needed about half an hour. The rest was people saying yes. This is what The First Fix puts on your app.

Read the full trail

Built on experience shipping real apps.

Seven years, ten-plus apps, hundreds of thousands of users.

Mobile · Digital insuranceSejfa10,000+ usersReact Native · Shared mobilityGoShareBoth stores, ongoingMobile · Backend · AIGymplyOur own app, on the workflowFull-stack · FintechLocked MoneyFull-stack web platform

One fixed price to start. One plan to keep going.

In SEK, ex VAT.

The First Fix

Start here

20 000 SEK one fixed price

The workflow on your app, and the first fix from your backlog on your phone. Within five working days of access, or it’s free.

Invoiced when the first fix is on your phone. Not before.

Book a call
Included
  • Access review on day one, in writing
  • Tests and builds to TestFlight and Play
  • The workflow, installed in your repo
  • Your backlog read, in plain language
  • The first fix: report, diagnosis, pull request, build
  • Code, workflow and record in your accounts, yours if we stop

A second app or a backend repo: +10 000 SEK each. Nothing else.

Then keep it going.

Month to month. Price held for twelve months.

Keep it working10 000 SEK/ month5 changes a monthBug fixes from your backlog.First two apps: 5 000 SEK a month.
Keep improvingRecommended20 000 SEK/ month10 changes a monthFixes plus small improvements. A monthly call.
Keep building50 000 SEK/ month25 changes a monthNew features. About a day of engineer time a week.

One change is one request that becomes one build. Extra change 2 500 SEK. New app? From 50 000 SEK, both stores.

Frequently asked questions.

What counts as a change?

One request in plain language that becomes one test build. “A finished workout shows as not done after a reinstall” is a change. “Redesign the workout screen” is several, and we tell you how many before we start.

Our app was built by someone else and it’s a mess. Does that matter?

No. Any React Native app, any state. Nine in ten pay the base price, and the two exceptions are listed with the price. If tests, a build pipeline or a release setup are missing, we add them as part of The First Fix.

What do you need from us to start?

Access to the repo, App Store Connect and Google Play Console in your company’s name, one person who can approve a build, and a phone with TestFlight. We start once those are in place. If they can’t be arranged within ten working days, nothing is invoiced.

What happens when the workflow can’t make a change on its own?

It goes to the engineer. Same count, same price, and it may take a few days longer. Store rejections and logic bugs always go to the engineer.

Who’s responsible if AI-written code breaks something?

We are. An engineer reads every change before it’s built and signs every release. You approve every build on your phone before it ships.

Can we pause or stop?

The plan is month to month with 30 days’ notice. Everything is in your accounts, so stopping means you keep everything. The next engineer picks it up from the repo.

Is our code used to train AI?

No. It runs through Claude under commercial terms that don’t allow that. It’s used for your app and nothing else, and our copies are deleted within 30 days of stopping.

Do you work with Expo? Old React Native versions? Flutter?

Expo and bare React Native are the focus, any version. Flutter and native Swift or Kotlin apps work too, since the engineer writes native iOS and Android as well. We scope those on the call.

How is this different from hiring a developer or an agency?

With a developer you pay a salary and still have to direct the work. With an agency you pay by the hour, small fix or not. Here the price is fixed. The workflow does the routine work, the engineer reads and signs each change, and you talk to the engineer directly. There’s no account manager in between.

We’re not in Sweden. Does that work?

Yes. We work across the Nordics and in English. Prices are in SEK, invoiced ex VAT.

See if The First Fix fits your app.

Twenty minutes on your app and where we would start. No slides, no sales team.

Alvar Aronija, triplefive
Book a 20-min intro callPick a time that suits you.
Book a call
Prefer to email?alvar@triplefive.io