Money tracker

Money tracker – Fynza

Designing, building, and launching a small iOS product

Download on App Store

Fynza was a small product with a useful constraint: ship fast, keep the scope focused, and learn the full path from design to App Store release.

I worked with a marketer, studied the niche, simplified the core expense flow, and built the app myself instead of stopping at mockups.

The project covered UX, SwiftUI implementation, branding, App Store assets, onboarding, and paywall logic — a compact end-to-end release.

7 days

from idea to App Store

Idea and wireframes

User flow and architecture

I started with the smallest useful expense flow: one clear home entry, fast adding, optional analytics, and minimal settings. The goal was not to copy finance apps, but to keep the product easy to understand and quick to ship.

Home

I want to quickly see spending for the period. I want to know the total. To understand how much I spend.

Add

I want to add an expense in a few seconds. Enter amount. Pick a category or create one. So I can easily read the list and charts later.

Summaries and charts

I want to check summaries from time to time. I want to see spending structure. To understand the trend and not rely on gut feeling.

Development

Building the app in Xcode

I built the app shell in Xcode, structured screens, and used AI-assisted development carefully rather than treating it as autopilot. The process forced me to understand SwiftUI, fix UIKit issues, and keep the implementation close to the original product logic.

First prototypes

At first I trusted AI. Wanted to build fast and painlessly. Spoiler: the pain still came.

The struggle

While learning, I kept changing approach. One way, then another. Ended up with something that looked like an app. But the design had to stay flexible. Lacked practice and didn’t want to box myself in.

Back to the base scenario

After experiments, returned to the original idea. Laid it out by hand. By then I understood the syntax. And knew where to look and what to fix.

App Store marketing

Working on the listing

I underestimated this at first. Then realized a simple thing: without packaging, the app won’t be seen. Looked at competitors. How they frame the value. What screens they use. What they put in the first seconds. Discussed a lot with the marketer on how to sell it.

References

First shock was strong. Some references looked like scams. But that’s part of the market too.

Drafts

Tried to mix aggressive patterns with my content. Felt odd. I’m used to whitespace and calm colors.

Finally done

Found a compromise. Made bigger headings and stronger elements, but didn’t turn it into a banner. Toned down the background. Softened the layout with cards. Left enough room for text.

Icon

Simple idea: dollar and scanner. Did it neatly with right proportions. For light and dark theme. Looks good on the home screen.

Onboarding

Justify the purchase

If someone has already downloaded — don’t lose the moment. Made a short three-screen onboarding. Then — paywall. Closed the app and added first expense — paywall again. Yes, it’s a trend. And yes, it works.

Shell

To avoid suffering with themes and translations, made a universal shell. It handles any text length.

Xcode

Built one shell first. Filled content from code with static data. Faster to check logic.

Result

Onboarding came together calmly. By then I had a sense of how to do it faster and with fewer mistakes.

Conclusions

Logic and screens first. Pretty pixels later.
A build plan in Xcode is needed upfront. Otherwise it’s a quest.
Marketing and onboarding eat time. That’s normal.

Other projects

Part Production Cell — MES & OEE

OpenPLC, Ignition Perspective and SQLite: order in events, KPIs and downtime causes.

View case study

Conveyor Sorting

OpenPLC and Ignition: ladder logic, a Structured Text state machine, sensor feedback, and verifiable normal cycles.

View case study

Monitoring — UPL

Enterprise monitoring for a nuclear plant: system states, engineering constraints, and 3D storage logic.

View case study