From competition idea to product
Finance Flow began as a team entry in a 36-hour Econverse startup sprint. Our team later placed third in the national grand final at the European Financial Congress. I own the engineering: the mobile application, school dashboard and backend. Most of the product was developed after the competition.
The product lets students practise financial decisions and see their consequences. I am developing it in collaboration with schools, with a separate dashboard for the classroom workflow.
Decisions that change the next step
A financial simulation needs more than a correct answer. Income can arrive later, money set aside for an obligation must stay protected, and an earlier choice can change what the student can afford next.
I built branching cash-flow scenarios around those rules. Tests explore valid decision paths and starting budgets, checking that balances stay consistent and that students can reach an ending. This catches cases where a plausible individual choice leaves the rest of a scenario impossible to complete.
Rewards that stay consistent
Repeated requests and simultaneous updates must not award progress twice. I implemented reward updates in PostgreSQL transactions with row locking and duplicate checks, so the completion record and its rewards are applied together.
This moves the consistency rules into the database, where they can cover requests from both the mobile application and the school dashboard.
One product across mobile and school workflows
The student app uses React Native and Expo. The school dashboard uses Next.js, with Supabase and PostgreSQL behind both. I develop these parts together so the same learning and progress rules serve individual students and classroom use.
Visit Finance Flow