ChatGPT Image 2.0 created the design. Codex GPT 5.5 turned that design into a full Expo React Native app From asset generation to music logic, everything handled by ChatGPT using just a referenced design image 🔥 Is this what the future of development looks like?

wild how the bottleneck moves from coding to taste

It was meant to be this way all along :)

Looks awsm. Im trying to do this but Codex struggling. What prompt u used?

It wasn't a single prompt but rather three prompts for three screens. One of those was a main starting master prompt that sets the tone of development like I specify role for AI, dos and dont's, tech requirements, design theme, code practices, and telling it to use imagen skill of Codex. Kind of template that I follow. You can generate this using AI by telling it to create a prompt based on your defined template.

@Mohamma98127565 I actually use ChatGPT to generate Codex prompts. Seems to work well. Especially since most of the time ideas just come out of my head talking to ChatGPT. So it formats it well.

@Mohamma98127565 If you clearly tell an AI what you want these days, it can almost do your work correctly. All of them are almost equally capable of getting things done. Your output depends on your input :)

Love it. Make the casette spin while playing just like the real thing did. add an animation that opens the case and switches cassettes when playing the next song. Would be awesome

It's already in my bucket list. It's fun to do such experiments!!

If only it could take the image and actually make it look that cool instead of a flat mimic in a real app.

It can do that too but I wanted a playable retro music player in shortest amount of time possible :D

古き良きwinampやん😃

Yeahh, I love that retro music device feel so I made it on purpose :D

thats looks cool

this is wild bro ChatGPT literally built the whole app

Man how come i am the only one who cant figure out it yet!!

Expo here. Screens are solved. Auth, offline sync, locale stuff still hand work.

I'm actually implementing all of these for my next vibe coded project. You won't believe but it's very easy when you break down your features in chunks and provide Agent enough context :)

Offline sync vs i18n is where chunks run out of road :) Bug class lives in the seams between features.

Sorry, but could you be any less ChatGPTish? :D

Last time used Chatgbt was 5 months ago believe it or not

Feels like designer and developer roles are converging. But great work still needs both 🙂

still needs a lot of adjusting after initial start

No one should feed their customers with AI slop UI

I have been trying to do this as well, designing with GPT and then development with Claude. Can you advise on the prompt you gave to GPT to generate this type of design, not the exact design but a general UI/UX prompting guide?

What was the reference image?

the bottleneck just becomes finding what it lied about

Keep Going!!

Wild how fast the gap between design and working app is closing. A year ago this would've taken a team weeks.

nice demo but if you can't charge clients for the output it's just a hobby project.

These nice demos will bring in clients, which I’ll then charge :D

Looks so good

Looks cool

One-shotted?

Might have been possible, but doing that exhausts credits faster. I did it in three prompts almost, one for each screen :)

This is hella impressive!

@emilyrtt1

Design → full app from one image… dev workflow just got compressed like crazy

那很神奇操作玩法

@TheRealAdamG insane

@TheRealAdamG Thank you :D

How do you go from image to code? I need to know.

It starts with a master prompt. This prompt defines everything from its role, design theme, code practices, dos and dont's, technology, and such. I do that by providing an image of the design and my usual prompt template to the AI. It then extracts design themes from the image and creates a master prompt. From there I paste this prompt in Codex alongside the design image. For anything next, I tell it what it has to do in simple words as by this time AI already has context of who it is and what it has to do due to the master prompt :)

what was the original prompt?

idk if I fully agree here, feels like this only works in theory, what about maintenance and debugging?

I've been testing an approach to maintaining vibe coding applications in the long run. If you make your Agent aware of your coding practices and design tokens every time you add a feature or try to debug a bug, it goes well with outputs. So far this is working for me and based on that I can for sure say that it's possible to maintain mid projects through vibe coding in the long term :)

Tell that to the retarded designers on LinkedIn

Oh no, they only understand, "I'm happy to share..."

Wild. Just built a delta robot arm that parses hand-drawn sketches into G-code—same vibe, different stack. Curious how it handles edge cases like ambiguous UI states or async music timing? 👀

The gap between "I have an idea" and "I have an app" just collapsed to a weekend. The founders who move fast in the next 6 months are going to eat everyone else's lunch.

Personally, this style isn't really my thing.

That's okay. Not everyone has to have common liking or preferences :D

@hlinhbuilds especially not now, when it's this easy to create your own software

@hlinhbuilds Rightly said!!

woo, amazing