The Journey of Actua

Actua started as a simple idea: I wanted a better Android experience for Actual Budget.

I was already using Actual Budget and liked the philosophy behind it. It gave me the flexibility I wanted for managing my finances without locking everything into a proprietary ecosystem. But on Android, I wanted an experience that felt more natural, modern, and at home on the platform.

That curiosity eventually turned into code.

From Actuali to Actua

The project did not start from a completely blank page. It grew from Actuali, an Android client for Actual Budget, and gradually became something I wanted to maintain and shape in my own direction.

Along the way, the project was rebranded as Actua.

The goal was not simply to change the name. I wanted to build a polished Android client around the Actual Budget experience while keeping the project open source and making useful features available without putting them behind a paywall.

Learning by building

One of the most interesting parts of the journey has been discovering how many small details matter in a finance app.

Transactions need to feel quick and predictable. Account balances need to be clear. Category selection needs to be easy. Reconciliation needs to stay focused. Animations should feel smooth rather than distracting.

Then there are the less visible parts: bank synchronization, imports, reports, account organization, edge cases, testing across Android versions, and making sure changes do not break existing workflows.

Many of Actua’s features started as small ideas or GitHub issues and then evolved through implementation, testing, feedback, and iteration.

From code to real users

A major milestone was taking Actua beyond my own development environment and into Google Play closed testing.

That changed the nature of the project.

It was no longer just about whether something worked on my phone. Other people had to be able to install it, understand it, use it, and report problems. Play Store requirements, tester enrollment, release management, issue tracking, and community communication all became part of the project.

The Actua community also started taking shape around GitHub, Discord, and the Google Play testing group.

Building in public

One thing I have particularly enjoyed is building Actua in public.

Ideas become GitHub issues. Issues become pull requests. Pull requests become releases. Feedback turns into another issue, and the cycle starts again.

Some features are tiny improvements that most people may never notice. Others change how the app is used. Account reordering, account groups, transaction workflows, category improvements, reports, synchronization, and many other changes have all come from that continuous process.

That is what makes open source interesting to me. The project is never really finished.

Where Actua is today

Actua has grown considerably from the small Android project I started with.

It now has a growing feature set, Google Play distribution, an active development workflow, a community around it, and a roadmap that continues to evolve alongside Actual Budget.

There is still a lot I want to improve.

I want Actua to feel fast, polished, familiar, and genuinely useful every time someone opens it. I also want to keep the project accessible and open, with features available to everyone rather than gradually turning it into a collection of paid unlocks.

What comes next

I don’t have a grand startup story behind Actua.

It is simply a project that grew because I wanted to solve a problem, enjoyed building the solution, and kept finding things worth improving.

From a small Android experiment to something that other people can install and use, the journey has already been much bigger than I expected.

And I’m still building.

If you use Actual Budget and want to follow the project, Actua is available on GitHub and Google Play. Feedback, bug reports, feature ideas, and contributions are always welcome.