The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
One thing I learned migrating a mobile product from a WebView MVP to React Native: the hardest problems usually aren't the screens.
On Beepr, the real blockers were background execution, geolocation reliability, push notifications, slow geospatial queries, and backend logic that had grown without a clear audit trail.
I led the migration to React Native with Supabase, PostgreSQL, PostGIS, and native background capabilities. I also audited 51 Supabase Edge Functions and designed a zero-downtime cutover so the product could keep serving users during the transition.
The takeaway: before rebuilding a mobile app, find out which problems are architectural and which are merely visual. A prettier interface won't fix unreliable background services, weak location enforcement, or slow queries.
Curious what other teams have found when moving from a WebView-based MVP to a production mobile app.
8:58
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
Claude
Claude has entered the design space. How are you using it?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
Brand Design
The best brand designers are on Contra. Scroll to see what's trending in brand design. What are you building?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?
Related posts
Excited to share my submission for the #FlowstepChallenge!
I designed Maven AgriConnect, a mobile marketplace that connects farmers, buyers, and logistics providers in one seamless experience. Starting with Flowstep AI, I refined the concept in Figma to create a role-based product focused on usability, trust, and efficient agricultural commerce.
Tools: Flowstep AI • Figma
@flowstep_ai
#UIDesign #Figma #ProductDesign #Marketplace #MobileApp
GULP. Mobile App. Meet.Gulp.Connect.
View the Prototype Here: https://app.flowstep.ai/file?activeFileId=e36b3a5f-498f-4f70-9739-dc453f3e49eb
What is GULP? And What does it do?
Basically, GULP makes business cards obsolete.
With a simple tap, two people can instantly exchange the contact details they choose to share—phone, email, website, social profiles, résumé, and more. No typing numbers, no QR-code juggling, and no forgotten cards at the bottom of a bag.
Here’s how it works: users create a polished GULP profile by adding their name, photo, short introduction, profession, contact details, social links, and—if relevant—their résumé. Before sharing, they decide exactly what is visible using simple on/off controls for every item.
When two GULP users meet, both open the app’s sharing screen and bring their phones close together. Using NFC, GULP securely exchanges the information each person has chosen to share. The recipient immediately sees a sleek digital profile and can save the phone number, add the email, visit a website, follow social accounts, or keep the profile in their GULP directory.
Unlike a paper card, GULP stays current. If someone changes their email, phone number, role, or social profile, they can update their GULP profile and re-share it—updating the existing connection instead of creating another duplicate contact.
Built for iPhone and Android, GULP turns real-world introductions into useful, living connections: beautiful, private by design, always current, and ready in one tap.
GULP. Meet. Gulp. Connect.
UI Factory — The Alert Component
I've been building interfaces for a while now. And for most of that time, I did what everyone does — reached for a library, dropped in a component, tweaked the colors, shipped it. Job done.
But I kept noticing something. No matter how polished the product, the UI always felt borrowed. Like you could see the seams of whatever design system was underneath. Everything started looking the same.
So I decided to start building my own things from scratch. No templates, no defaults. The rule I set for myself: every component has to have its own identity. Its own material, its own physics, its own personality. A notification alert shouldn't feel anything like a pricing card. A dock shouldn't feel like a modal. Each one is its own experiment.
This alert component was the first one I finished. I wanted it to feel physical — like something you could reach into the screen and peel off. That drove every decision: the shadows, the spring physics, the way the stack fans out when you hover it, the way each card exits with a little spin. Nothing about it is accidental.
But claymorphism is just one direction. The library I'm building will go everywhere — glass, depth, brutalism, motion-first, 3D. The point was never an aesthetic. The point is that UI can feel crafted instead of assembled.
I'm in the early stages of building my own UI component library. If this work gets traction, the plan is to open-source the full code so designers and developers can use these in their own products. Every component ships with its own philosophy — no two will feel the same.
This is just the beginning. Follow along.
→ Try it yourself: https://ui-factory-zeta.vercel.app/notification-stack
Stack: React 19 · Next.js 15 · Framer Motion · TypeScript
#SoftwareArchitecture #SystemDesign #FullStack #SaaS #AIEngineering #DistributedSystems #React #PostgreSQL #NodeJS #Python #ProductEngineering #WebDevelopment
The spring physics and layer depth look incredible in action! Crafting components from scratch with true physical personality beats cookie-cutter UI libraries every single time. Awesome work!