03 / Engineering storyInvestSky · Lead Software Development Engineer · May 2023–Dec 2024
InvestSky✳
A better feel for finance.
Owned the React Native rebuild from architecture through release. A cohesive design system and responsive financial interfaces, shipped across iOS and Android.
React NativeDesign systemsReanimatedFintech
80%Reported performance improvement
20%Reported engagement lift from launches
iOS + AndroidArchitecture through release
01 / The challenge
A product problem,
not just a screen.
A financial mobile app has to make dense data, dynamic forms and long lists feel coherent on a small screen. The rebuild needed a common UI foundation across Android and iOS, with performance and release ownership treated as part of the same engineering problem.
What I owned
As the sole mobile-app architect, I owned architecture, delivery and release end to end. I led the ground-up React Native rebuild and built the shared UI foundations, schema-driven forms and custom financial charting components.
The system, made visible
Explore the mobile foundations
Conceptual view of the frontend responsibilities. No proprietary screens, code or internal architecture documents are reproduced.
Styled Components-driven design-system primitives underpin the ground-up React Native rebuild.
02
Data & motion
TanStack Query manages server data; FlashList and Reanimated support performant lists and animated interfaces.
03
Product systems
JSON-schema-driven forms and custom financial charts express recurring financial-product patterns.
04
Release
I owned architecture, delivery and release end to end across Android and iOS.
02 / Engineering decisions
01
Make the design system the foundation of the rebuild
What I built
I rebuilt the app around a Styled Components-driven design system.
Why it matters
Shared primitives give financial screens a common visual language. The architecture supports consistency across the two mobile platforms without rebuilding each screen’s foundations.
02
Give lists, data and animation dedicated tools
What I built
I adopted TanStack Query, FlashList and Reanimated for server data, high-performance lists and animation.
Why it matters
These are different concerns with different performance characteristics. The rebuild gave each an explicit place in the frontend architecture.
03
Turn recurring product patterns into systems
What I built
I built a JSON-schema-driven form engine and custom charting components for financial data.
Why it matters
Configuration-driven forms provide a reusable way to express changing field structures. Custom charting components address the presentation needs of financial data.
03 / Evidence & results
A ground-up mobile rebuild with a shared design system, reusable product primitives and reported improvements in performance and engagement.
The 80% performance improvement and 20% engagement lift are results reported in my résumé. Benchmark methodology and internal analytics are not reproduced here. The portfolio phone graphic is an original interaction study, not an InvestSky screen.