How apiko-dev/perfi works
Project type and purpose
• This is a React Native mobile app (“Perfi”) for personal finance management, bootstrapped with Create React Native App (Expo).
• It’s a front-end–only codebase (no standalone backend code) that uses Redux for state management, React Navigation for screen flow, and Expo to package for Android/iOS.
File structure
• Top-level config files (.babelrc, .eslintrc.js, flowconfig, package.json) and scripts (npm start, ios, android).
• app/
• assets/ (fonts, images, svgs)
• components/ (reusable UI widgets)
• modules/ (Redux ducks: actions, reducers, operations, selectors, types per domain)
• navigation/ (navigator containers, drawer, route definitions)
• screens/ (screen containers + views per feature)
• store.js (Redux store setup)
• styles/ (global style tokens)
• utils/ (helpers, HOCs, enhancers)
• tests/ (unit tests for reducers)
README for additional insights
• Confirms it’s an open-source personal finance management app, installs via Expo, uses React Native CLI if ejected, no explicit backend—data likely local or via mockData.
Elements
• Clear labels for each layer and component.
• UI → Redux actions
• Operations → store updates
• Store → selectors → UI
• Navigation → screen transitions
• Purple ovals = Assets/Constants