6
I built a calorie counter app using Next.js + TWA — looking for feedback on UX and bugs
r/indiehackers
6/28/2025
SAAS TOOLS
| SaaS | URL | Category | Features/Notes |
|---|---|---|---|
| Next.js | https://nextjs.org/ | Web Framework | Used for building the app |
| Trusted Web Activity (TWA) | https://developers.google.com/web/android/trusted-web-activity | Android Packaging | Used to package PWA for Android |
| PeerPush | https://peerpush.net | Community/Feedback | Platform for indie makers to connect and get feedback |
| Noom | Not provided | Health/Calorie Counter | Benchmark app with habit-forming features, mentioned as having app lag issues |
| SnapCalorie | Not provided | Health/Calorie Counter | Benchmark app mentioned for comparison |
USER NEEDS
Pain Points:
- App lag in calorie counter apps hinders daily habit formation
- Lack of iOS version limits accessibility
Problems to Solve:
- Creating a quick, light, and ad-free calorie counter app
- Ensuring app responsiveness and speed for better user experience
- Making the app user-friendly and intuitive
- Expanding app availability to iOS users
Potential Solutions:
- Optimize app performance to reduce lag
- Open source the PWA to enable community contributions for iOS version
- Use platforms like PeerPush for gathering feedback and visibility
GROWTH FACTORS
Effective Strategies:
- Building a lightweight, ad-free app for better user experience
- Using PWA and TWA for cross-platform compatibility
Marketing & Acquisition:
- Seeking feedback on communities like r/indiehackers
- Leveraging PeerPush for connecting with other indie makers and gaining visibility
Monetization & Product:
- Focusing on ad-free experience as a differentiator
- Potential open-sourcing to build community support
User Engagement:
- Actively soliciting user feedback for improvements
- Considering community contributions for feature development (e.g., iOS version)