Skip to content

Digital lending · Senior Flutter Developer · 08/2019 — 03/2021

Good2Go Loans

A digital lending app used by 50,000+ people across New Zealand — onboarding, authentication, account journeys, and store releases owned end to end.

Good2Go Loans logo

Good2Go Loans

Beedev Solutions · FinTech

Engagement
Aug 2019 — Mar 2021
Role
Senior Flutter Developer
Reach
50,000+ users
Market
New Zealand

The brief

Challenge

Lending products earn trust in the first few minutes. Identity, eligibility, and account access have to be clear, fast, and correct on the phones people actually carry — and the app has to satisfy financial-product review on both stores, release after release.

Stack

FlutterDartClean ArchitectureSOLIDREST APIsPush notificationsiOSAndroid
View on the App Store

What I did

  • Built onboarding, authentication, account journeys, notifications, and API integrations.
  • Designed a scalable Flutter codebase on Clean Architecture and SOLID principles.
  • Owned Android and iOS deployment, monitoring, and continuous improvement.
  • Worked directly with the lending team on product changes and release requirements.

Engineering decisions

  1. 01

    Clean Architecture and SOLID boundaries from the first release

    Lending rules, eligibility checks and identity requirements change with regulation and product policy. Keeping domain logic away from UI code made those changes local instead of app-wide.

    Trade-off More files and interfaces than a screen-first build, and the team had to agree on the boundaries.

  2. 02

    Authentication and account access treated as core journeys

    Trust is won or lost in the first minutes of a lending product. Errors, retries and session expiry received as much design attention as the happy path.

    Trade-off Closer coordination with backend and compliance, and slower iteration on those flows.

  3. 03

    Own both store pipelines through production

    Shipping Android and iOS ourselves kept release timing and rollback decisions with the team that wrote the code.

    Trade-off Release engineering and store review work never sat with QA or a separate release team.

Outcome

50K+ users in New Zealand

The product reached 50,000+ users across New Zealand, and the architecture became the base the team kept extending rather than rewriting. Releases stayed predictable on both platforms for the life of the engagement.

Have a similar project?

I can own the build from architecture to production support.

Talk about your project