Budgeting Prompt
Build a complete, production-ready native iOS app in Swift using SwiftUI. Use Core Data for all local data persistence. No login, no backend, no external APIs or third-party libraries.The app is a Personal Finance OS, a single place where a user manages their financial life from their phone.OnboardingA multi-step onboarding flow that runs only on first launch. It must feel premium, not generic. Step 1: Welcome screen with a value proposition, make it feel like a product, not a tutorial Step 2: User enters their full name and selects a currency from a searchable list of at least 10 currencies Step 3: User sets their monthly net income Step 4: User selects their primary spending categories from a predefined list (minimum 10 options) with the ability to add a custom one. Minimum 3 must be selected. Step 5: User sets a monthly savings goal as either a fixed amount or a percentage of income , they can toggle between both Step 6: Summary confirmation screen showing everything they set up with an edit option before finishing Progress indicator throughout. Ability to go back to any previous step. Tapping outside a field should dismiss the keyboard. Core Features1. Dashboard (Home) The first thing the user sees every day. Must include: Personalized greeting with the user's name and current date Current month's financial summary: total income, total spent, amount remaining Savings goal progress bar with percentage and amount remaining to goal Financial Health Score (0–100) displayed prominently with a label (Poor / Fair / Good / Excellent), score is calculated from: savings rate, subscription load relative to income, and whether spending is trending over or under budget A spending trend sparkline or mini chart showing daily spend for the current month Quick-add button to log a transaction without leaving the dashboard A "top spending category this month" callout 2. Transactions Full transaction log sorted by date, grouped by day Each transaction shows: amount, category icon and name, optional note, date Add, edit, and delete transactions Transaction form: amount (with a proper numeric pad, not a text field), category picker, date picker, optional note Filter transactions by category, date range, and amount range Search transactions by note or amount Empty state with a clear call to action 3. Spending Breakdown Visual chart (pie or donut) showing expense distribution by category for the selected period Period selector: current month, last month, last 3 months, custom range Below the chart: a ranked list of categories with amount, percentage of total, and a bar indicator Tapping a category drills down into its transactions 4. Subscriptions Tracker List of recurring expenses with: name, amount, billing cycle (weekly, monthly, yearly), next payment date, category Monthly and yearly cost calculated automatically Subscriptions due in the next 7 days should be visually flagged Add, edit, delete subscriptions Total monthly subscription cost shown at the top relative to income as a percentage Empty state 5. Financial Health Score: Detail Screen Full breakdown of how the score is calculated Each factor shown individually with its contribution to the score Plain language explanation of what's dragging the score down and what's helping it One actionable tip based on the user's actual data 6. Settings Edit name, income, and savings goal Manage categories: add custom, rename, delete (with a warning if transactions exist under it) Currency selector Subscription management shortcut Reset all data option with a confirmation dialog A conditional (when running in debug mode) button to generate sample data to test all the features of the app App version and a "built with SwiftUI" note Design RequirementsNo design system is specified. You must make your own decisions. However, the app must feel like something that could be on the App Store today, not a student project. Dark mode support required Custom app icon concept (describe it or generate it) Every screen must have a defined empty state Loading states where applicable All transitions and navigation must feel native and fluid Micro-interactions expected: button feedback, progress animations, score reveal animation on the dashboard, chart entry animation Typography hierarchy must be intentional, not everything the same size No placeholder UI, every screen must be complete Technical Requirements SwiftUI only, no UIKit unless absolutely necessary MVVM architecture Core Data for persistence with proper relationships between entities The app must run without crashes on first launch, after onboarding, and after a data reset Handle edge cases: zero transactions, goal not set, all categories deleted, single transaction in a category
Get it → egoiscof.gumroad.com