Mobile App Development for Expense Tracking
An expense tracking application is not budgeting, not investing. The main priority here is speed of entry. If a user needs more than three taps to record spending 200 rubles on coffee, they'll abandon the app in a week. Everything else (analytics, limits, export) is secondary.
Speed of Entry as an Architectural Task
Fast expense entry needs to be designed at both the UX and implementation levels simultaneously.
On iOS: Home Screen widget through WidgetKit with AppIntent (iOS 16+) opens an input sheet without launching the full app. INAddTaskIntent / custom Shortcut lets you record expenses via Siri voice. Live activity in Dynamic Island shows daily balance without unlocking the screen.
On Android: Tile in Quick Settings through TileService — one swipe and tap, the app doesn't fully open. Floating widget over other apps through WindowManager (needs SYSTEM_ALERT_WINDOW permission) — questionable from UX perspective, but some users love it.
Numpad for the amount — custom, not system: system keyboard adds 200–300 ms show delay. Auto-focus on amount field, category defaults to "last used", location estimate for category (Coffee shop nearby → "Food" category).
Categories and Limits
Categories with icons and colors, nesting maximum one level (subcategories). Monthly limits per category — store as separate BudgetLimit entity with categoryId, amount, month. At 80% limit — local notification. Progress calculation — only when opening the corresponding screen plus background recalculation through BGAppRefreshTask once an hour.
Analytics and Export
Charts: pie chart by categories for a period, column chart by day. On Flutter — fl_chart, on iOS natively — Swift Charts (iOS 16+). Don't use heavy libraries for two simple charts.
Export to CSV and PDF. CSV is trivial. PDF through PDFKit (iOS) or PdfDocument (Android) — render expense table with totals. Important: user should be able to select period and category set before export.
Sync and Multi-Device
If sync is needed — Firebase Realtime Database or Firestore with merge logic. Main trap: conflicts on simultaneous writes from two devices. Strategy: last-write-wins by updatedAt timestamp for simple cases, or CRDT for complex. For most expense trackers last-write-wins is sufficient.
Work Process
We clarify: whether sync between devices is needed, single user or family account, whether bank statement import is needed, target platforms. We design data model accounting for scale (one year of expenses = thousands of records, not much).
Timeline Guidelines
Basic tracker with fast entry, categories, limits and CSV export — 3–5 weeks. With widgets, PDF reports, CloudKit/Firebase sync and charts — 7–10 weeks. Pricing is calculated individually.