Budgetr currently has three components: DLL, C# MVC webapp and WinForm.


The spreadsheet I use for budgeting is better than yours. Probably.

My confidence prompted me to create a Groovy/Grails webapp based on the same principles – the best part is it counted towards my FdSc Software Engineering because I created it for an assignment!

A UML from the early model. Many changes to the formula since then but account, transaction and recurrence are still at the core.

I used Groovy and Grails (version 2.4.4) framework and my unit testing helped me gain a good grade.


In my first year at UEA, just after attending Sync the City 2016, I decided I had to learn C#. After an intensive week, a functional Budgetr.dll was built.

A few months later, I signed up for MS Imagine and was compelled to get comfortable with C# ASP.NET MVC. After twelve days, I launched Budgetr as an Azure webapp.

The github page shows 31 commits. The first twelve were in April 2017, followed by two bursts of activity in June and August/September 2017.

The reason for subsequently undeploying was quickly apparent: it isn’t feasible to get anyone to test an online prototype where personal financial data is then exposed to the developer – and I didn’t much fancy the banal task of making the data more secure just to end up with a webapp which was coupled tightly to Microsoft’s services.

Besides the technical reasons, I crave intuitive and simple UIs even if the purpose is complex. The Azure portal gave me nightmares to match my Oracle and Google ones.

Besides, I learned C# ASP.NET with some OAuth (Facebook login) sprinkled on top: the project was a success.

I also revisited the Budgetr library code, adding COM interoperability to open the possibility of using Budgetr.dll a bit more flexibly.

29th September 2018

Guess who’s back?

It’s me. Or Budgetr. Depends how you look at it. It was a poorly phrased question.

For the sake of wanting more to show for all the long hours, I’ve just started Budgetr For Windows.

This is a Windows Form application, consuming the Budgetr.dll to expose the model as a Windows-only desktop application.

Warning: Unsexy UI detected. In my defense, we all get to interpret The Agile Manifesto differently.

The Future

My aim is to expose all features of Budgetr in this desktop application and then dive into some usability testing (read: coerce friends and family to use it).

I hope to later open-source the Budgetr library, as well as the ASP.NET webapp and Windows application to serve as examples of usage.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s