Menu

The last 20% of an AI-built app: nine things that actually block launch
πŸ“°

The last 20% of an AI-built app: nine things that actually block launch

DEV Community: javascriptΒ·Youngjun YoonΒ·about 11 hours ago
#bkRWiwLj
#devtojavascript#devto#dev#symptom#happening
Reading 0:00
15s threshold

I keep hearing the same story from people who built something real with Cursor, Lovable, Bolt, v0 or Replit: the app exists, the demo works, and it has been "almost ready" for two months.

The 20% they are missing is rarely a feature. It is a set of integration seams that a generator will happily write code around and never solve. Here are the nine that block launches most often, in the order I check them, with the symptom and the fix.

1. Sessions that only exist in memory

Symptom: you can log in, and a refresh logs you out. Or login works on localhost and not on the deployed domain.

What's happening: the auth code stores a token in a module-level variable, or sets a cookie without Secure / SameSite , or signs with a secret regenerated on each cold start because it is generated at boot instead of read from the environment.

Fix: persist the session in an HttpOnly , Secure , SameSite=Lax cookie (or a refresh token in storage for mobile), keep SESSION_SECRET in the environment, and test after a hard reload,…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.