b.Uni

The context

University students have a financial life of their own: allowance, internship pay, first account, first card. b.Uni serves them with a digital account, Pix, transfers and cashback. I own both platforms — which means the same person who decides how a flow behaves in the app decides how it translates to the web.

Decisions that were mine

1. 01App and web as a single product

   I keep deliberate parity between the RN app and the React internet banking: same API contracts, same state modeling, same UI language. Moving from phone to desktop never means relearning the bank.

2. 02Predictable financial state above all

   Balance, statement and receipts can never flicker or diverge. I structured the data flow with Redux so every financial mutation has a single, traceable origin — which simplifies both debugging and auditing.

3. 03The details that make it feel like a real bank

   Shareable receipts, well-crafted empty states, instant feedback on every transaction. No requirement ever asks for these explicitly — and they are exactly what separates a trustworthy financial app from a prototype.

Where it landed

App and internet banking in production on the stores and on the web, evolving through continuous releases for the student base.