Inspiration

FunnelFlow was inspired by the growing subscription fatigue people feel every month, combined with the challenge app teams face when explaining the value of a paid subscription. We wanted to connect both sides: helping users understand their recurring spend while helping product teams design clearer, more trustworthy web-to-app paywall funnels.

What it does

FunnelFlow is a mobile dashboard for micro-budgeting, subscription tracking, and paywall funnel optimization. It shows projected savings, paid conversion, monthly tracked subscription spend, funnel performance, weekly budget limits, and upcoming subscription renewals. Users can switch between pricing plans, adjust a weekly spending cap, review subscriptions, and see how savings messaging could support a trial-to-paid conversion moment.

How we built it

We built FunnelFlow as a cross-platform Expo app using React Native and TypeScript. The interface uses Expo SDK 57, expo-linear-gradient for visual panels, react-native-svg for charts and progress visuals, and @expo/vector-icons for dashboard actions. We started with a focused single-screen prototype so the core product idea could be tested quickly on iOS, Android, and web through Expo.

Challenges we ran into

One challenge was balancing two related but different product ideas: personal subscription budgeting and web-to-app paywall optimization. We had to make the UI feel useful for both without becoming crowded or confusing. We also ran into Expo SDK compatibility issues and upgraded the project so it works with the current Expo Go version. Another challenge was making static prototype data feel realistic enough to communicate the product vision.

Accomplishments that we're proud of

We are proud of creating a polished mobile-first dashboard that communicates the product concept immediately. The app includes interactive plan selection, budget cap controls, subscription cards, funnel metrics, and custom SVG visuals in a compact experience. We are also proud that the project is now updated to Expo SDK 57, passes Expo validation, and has a clear design document for future development.

What we learned

We learned that subscription management becomes more compelling when it is connected to user outcomes, not just expense tracking. Savings, renewal timing, and budget confidence can all become part of a stronger paywall story. We also learned the value of building a focused prototype first: it helped clarify the main user flows, visual language, and future architecture before adding backend complexity.

What's next for FunnelFlow

Next, FunnelFlow could add real subscription data, persistent budgets, and create/edit flows for tracked services. We also want to turn the placeholder Publish action into a real paywall experiment workflow, backed by analytics and cohort-based funnel metrics. Longer term, FunnelFlow could support account linking, personalized recommendations, authentication, backend sync, and smarter suggestions for pausing, canceling, downgrading, or converting subscriptions to annual plans.

Built With

Share this project:

Updates

Submission history