Abhishek Patel

Arteza opens on a grid showing all six studios at once, image, video, voice, music, avatars, editing. It demos brilliantly. It's the screen people screenshot and it's why anyone understands the product in four seconds.

It's also the screen our heaviest users leave immediately. If you're in it every day you already know which studio you want, so a menu of six is six things to skip. The people who love that grid are the ones seeing it for the first time, and they only see it once.

The mistake underneath is that I designed the first thirty seconds and assumed the next thirty days would sort themselves out. Everything I measure at signup rewards that grid. Nothing I measure rewards the tenth session, so the tenth session never got designed.

Trying to make the home screen a function of what you did last week instead of a fixed grid, which is easy to say and quietly a different product. If you shipped something that demoed well, what did you have to change once people actually lived in it?

I used a few different tools to vibe code my saas. I used lovable, chatgpt, gemini to code my saas. The thing is, there is a huge problem of these AI's of forgetting when you chat for a longer time.

This has happened to me a lot of times. One solution I found is that you can start a new chat to overcome this problem. But, here the problem arises to explain the AI all the context which you had in the previous conversation.

Curious, has anyone else ever ran into this problem? How did you manage to overcome this?

I ve run into this with longer agent runs and I m curious how others handle it.

The original issue might contain the scope, constraints and evidence required. But when another model or session picks up the work later, those conditions often get reduced to a summary.