Fragmented Generation Workflows
The product could not launch as a pile of scripts calling DALL·E or a video API. Users needed one mobile experience for images and video, with accounts, history, and delivery that felt like a real product.
Senior AI Full Stack Developer
Arjun partnered with a consumer AI product team to ship a production-ready image and video generation platform that unifies mobile creation, multi-provider AI workflows, billing, moderation, and operations. The engagement covered full-stack product development, Google Cloud architecture, admin tooling, and App Store launch.
The client needed a unified way to offer AI-generated images and videos to mobile users — with reliable auth, subscription billing, content moderation, and operations tooling — not a collection of one-off scripts wired to a single model demo.
Arjun owned end-to-end delivery: native mobile creation flows, Node.js REST APIs, Firebase identity and data, an admin panel for users and analytics, subscription payments, and Google Cloud deployment so generation workloads could scale without rewriting the app.
The product could not launch as a pile of scripts calling DALL·E or a video API. Users needed one mobile experience for images and video, with accounts, history, and delivery that felt like a real product.
OpenAI, Kling AI, Seedance, and Nano Banana each have different latencies, failure modes, prompt shapes, and webhooks. The platform had to treat them as interchangeable adapters instead of hard-coding one vendor into the client.
Video generation is slow and expensive. Without server-side quotas, async jobs, and credit checks, paid APIs would burn budget and HTTP requests would time out.
When a job failed in production, support needed an admin view that matched what the user saw in the app — users, content review, usage, and analytics — not a hunt through logs.
Free-tier users could not be allowed to bypass entitlements. Subscription state had to be enforced server-side before any generation call hit a paid provider.
Arjun designed a production architecture where the mobile app submits a generation request, and the backend validates the user, checks credits, enqueues work, stores assets, and notifies the client when rendering finishes.
Built a single job flow for image and video requests so the iOS app never talks to model vendors directly. Prompts, aspect ratios, and status updates stay consistent across providers.
Implemented provider-specific adapters for OpenAI, Kling AI, Seedance, and Nano Banana, normalizing inputs and webhooks so vendors can be swapped without rewriting the mobile client.
Moved long-running video tasks off the request path with async job handling and object storage on Google Cloud, avoiding HTTP timeouts and keeping the app responsive while renders complete.
Used Firebase Auth and database layers for sessions, user data, and generation history, plus an admin dashboard for support, content review, and usage analytics.
Enforced rate limits, credits, and entitlements server-side before calls hit paid APIs, then shipped subscription payments and App Store release as part of the same production stack.
Users create images and videos from one mobile product, with generation history and asset delivery handled through the same backend pipeline.
The app submits a request once. The backend routes it to OpenAI, Kling AI, Seedance, or Nano Banana without exposing vendor complexity to the user.
A Node.js API layer validates users, enqueues jobs, and returns status updates so the mobile client stays thin and reliable.
Operations teams can review users, moderate content, and inspect usage without asking engineering to query production data by hand.
Generation jobs, storage, and APIs run on GCP so traffic and long-running video work can scale independently of the mobile release cycle.
Billing and entitlements ship with v1, so the product can monetize generation credits instead of launching as an unbounded demo.
Production platform shipped
Shipped a production platform spanning mobile, API, admin, and cloud — ready to scale generation workloads and monetize through subscriptions.
Unified generation pipeline
Generation no longer lives in one-off scripts. Image and video jobs share one pipeline, with async handling so slow video renders do not block the app.
Vendor lock-in dropped
Vendor lock-in dropped: new models can be added behind adapters without rewriting the iOS client.
Operations surface for support
Support and moderation gained a real operations surface. Admin views stay consistent with what users see in the app.
Paid APIs protected
Paid APIs are protected by server-side quotas and entitlements, so free-tier abuse does not hit the generation bill unchecked.