work/ Building TAX IOS APP
From understanding taxes to building an iOS experience
This project started as a design assignment around tax harvesting and grew into a personal exploration of how complex tax decisions can be made easier to understand. Through this work, I focused on designing for clarity first and then building the experience as an iOS app to learn how design intent translates into code.
{ iOS App }
ROLE
Product Designer
PLATFORM/TOOLS
Figma, Figma MCP, Swift, SwiftUI
STATUS
Design complete,
build in progress
GITHUB REPO
how this started
Turning an assignment into a product
SmartHarvest began as a design assignment around tax harvesting.
While working on it, I realised the problem wasn’t calculations or charts. It was confidence.
Most investors don’t avoid tax harvesting because it’s impossible. They avoid it because it feels unclear and risky.
That insight pushed me to take the assignment further and explore it as a real product, designing it in Figma and starting to build it as an iOS app.
{ The Figma Prototype }
That shift made me step back and clearly define the real problem.
The problem space
Why tax harvesting feels hard
Tax harvesting can reduce tax liability, but acting on it is difficult.From initial research, a few key problems stood out:
ltcg and stcg rules feel intimidating
eligible funds are hard to identify
exit loads and timing create hesitation
benefits are not always obvious
The core problem wasn’t execution.
It was helping users understand whether tax harvesting is even worth doing for them.
{ Explore the design in figma }
THE constraint
Scope and approach
To stay focused, I limited the scope to Indian tax regulations and mutual funds, and intentionally mapped the experience to three core screens that best represent the tax-harvesting journey. This helped me go deeper on decision-making and interactions instead of covering everything at once.
Instead of jumping into screens, I broke the experience into steps based on how users think.
IDEA
The approach and experience ( the core 3 screens )
I structured the product around how users think.
Evaluate to understand the portfolio and see if an opportunity exists.
Educate to explain eligibility and tax rules in context.
Execute to let users act only after understanding the impact.
This shapes the entire experience.
The dashboard stays simple, education appears only when needed, and actions are calm with clear warnings.
The product helps users decide. It never rushes them.
Every screen and interaction follows this order
The experience
Choosing the right structure for users
To keep the product focused, I mapped the experience to a few core screens.
Each screen answers a specific user question and moves them forward without pressure.
Personal dashboard (screen 1)
See if tax harvesting is relevant to your portfolio
Get a high-level view of potential tax savings
Understand key warnings and constraints at a glance
Portfolio analysis ( bottom sheet )
Break down eligible and non-eligible funds
Understand why certain funds qualify for harvesting
See tax impact summarised visually before taking action
Funds listing (screen 2)
Explore all funds with clear eligibility indicators
Identify exit loads, lock-in periods, and low-benefit cases
Compare options without committing to an action
Fund details
View performance and tax implications together
Understand risks and trade-offs in context
Take action only when everything is clear
Learning content (screen 3 )
Learn concepts like LTCG and STCG step by step
Access explanations only when needed
Build confidence without leaving the flow
Below, you can see the Figma designs and prototype that bring these screens and ideas together.
AI x CODING
Designing and building it
I designed the full system and interactive prototype in Figma and started building it as a native iOS app.
Design tokens synced using Figma MCP
Core components mapped to SwiftUI views
Interaction logic handled in code to preserve intent and interaction
Still learning and figuring out how to integrate apis ( and also bring in real world data and authentication)
why i was building it
Reflection
This project helped me think more clearly about how people make tax decisions.
Building parts of it in SwiftUI also helped me understand the gap between designing screens and writing real code.
It’s still a work in progress, but it reflects how I like to approach problems: simple, focused, and intentional.
╌╌ END ╌╌