Poppy AI Payment Automation and React Flow Performance
A DevThinks case study on Poppy AI work across payment automation, subscription tracking, React Flow performance, UploadCare, documentation, tutorial videos, and LaunchMVP starter-kit development.
- Client
- Poppy AI
- Year
- Service
- Full-stack Development, AI Product, Payment Systems
Project Context
Poppy AI is a node-based visual AI workspace connected to Clever Programmer.
The product had around 1,000 paying customers, which meant small operational issues could turn into real support load.
Payment data needed to be easier to track. The React Flow workspace needed to stay smooth as users worked with visual nodes. Uploads needed to support normal user behavior, including Google Drive and Dropbox. The team also needed better docs and videos so product knowledge did not stay trapped in private chats.
Nasir worked on these areas during the Poppy AI engagement. The case study belongs on DevThinks because it shows a practical mix of frontend performance, automation, SaaS payment operations, and user support systems.
Payment Systems
Payment work is rarely just a Stripe button.
For Poppy AI, the business needed a clearer way to track:
- who paid
- how much they paid
- how much payment remained
- subscription and customer records
The automation work used Airtable, Zapier, Firebase, ThriveCart, Stripe, and PayPal.
That gave the sales and operations side a better record of more than 1,000 subscriptions and reduced the manual checking that usually creates mistakes.
React Flow Performance
Poppy AI used React Flow for its visual workspace.
Node-based products can get heavy fast. Once users add more nodes, edges, panels, and state changes, poor rendering decisions become visible. The product starts to feel slow even when the feature set is good.
The performance work focused on virtualization and reducing unnecessary re-renders. That is the kind of fix that protects the user experience without forcing a full rebuild.
Uploads, Docs, and Launch Support
Nasir also supported the product around:
- UploadCare integration
- Google Drive and Dropbox support
- technical documentation
- tutorial videos
- LaunchMVP starter-kit development
- Stripe payments
- Firebase Auth
- AI integration
These pieces matter because product quality is not only what happens inside the codebase. A SaaS product also needs the team and users to understand the flows without asking for help every time.
Stack
- React
- Next.js
- React Flow
- Tailwind CSS
- Firebase
- Stripe
- UploadCare
- Airtable
- Zapier
Why It Matters
Poppy AI is a good example of DevThinks-style work because the useful fixes were spread across product, payments, performance, and support.
The payment system needed accuracy. The visual workspace needed speed. The upload flow needed to match how users store files. The docs and videos needed to reduce repeated support work.
That is the kind of engineering that helps a product feel more reliable without turning every problem into a rewrite.