Projects using Supabase in City of LondonProjects using Supabase in City of London
Projects
People
Cover image for I built a productized AI
I built a productized AI workflow for ecommerce and marketing teams that need faster creative production without removing human review. The agent takes a simple campaign brief and product image, generates multiple creative directions, creates platform-ready captions, stores all assets, and sends the finished pack to Slack for approval. What It Does Takes product image, product name, campaign type, platform, and brand voice Generates 4 creative image concepts Writes 3 captions per concept Stores source and generated assets in Supabase Logs the campaign run in Postgres Sends a Slack approval card for review Keeps a human approval step before publishing Tools Used n8n, Claude, fal.ai (http://fal.ai), Supabase, Slack Best For Ecommerce brands, DTC teams, agencies, social media managers, and founder-led teams that need more ad creative without adding more manual production work. Outcome One brief becomes a structured creative pack: 4 visual concepts, 12 captions, stored assets, and an approval workflow ready for review.
0
118
Cover image for What’s the secret behind an
What’s the secret behind an app that actually feels good to use? It’s not just the UI. A beautiful interface can get someone to download an app. But good engineering is what makes them stay. When I build an application, I think beyond the screens users can see. The real work is happening underneath: ⚡ Performance — interactions should feel fast and intentional. 🧠 State management — the app needs to keep data consistent as users move through it. 🏗️ Architecture — the codebase needs structure that can survive new features. 🛡️ Error handling — things will go wrong; the app needs to handle them gracefully. 📱 Responsive UX — the experience needs to work across different screen sizes. 🧪 Testing — don't assume it works because the happy path works. 📊 Monitoring — understand what happens when real users start using it. That’s the part many people never see. A user taps a button and thinks: “That was smooth.” Behind that single interaction could be API calls, state updates, database operations, validation, loading states, error handling and performance decisions. That’s why I believe: A good app isn't just designed. It's engineered. Modern web performance guidance also emphasizes that loading, responsiveness and efficient resource handling directly affect the user experience. My goal isn't simply to build something that looks finished. I want to build applications that behave like real products. Idea → Architecture → Code → Test → Deploy → Real Users. What’s one thing that immediately makes you uninstall an app?
2
66