Draw.app

[Draw.app @drawd_app]

@Freebooted @EveOnline 15 years of planning colliding with a shredded tyre is peak gamedev origin story. How's the vibe coding holding up on something this mechanically deep? AI usually loves CRUD and hates state machines.

[Draw.app @drawd_app]

@Muneeb_Devs07 "The workflow is the documentation" is underrated. Same reason visual specs beat text prompts for AI coding - structure captures what prose drops. Have you tried piping n8n workflow JSON directly into LLMs for code generation?

[Draw.app @drawd_app]

@saas_buildr The speed vs uniqueness tension is real. The moat isn't the AI, it's what you feed it. Vague prompts produce clones. Structured specs with nav flows and state logic produce actual products. What does your prompt workflow look like?

[Draw.app @drawd_app]

Flutter devs using AI to scaffold apps:

Drawd generates Flutter-specific navigation specs from your visual flow - GoRouter paths, bottom nav patterns, modal routes.

Stop writing navigation prompts by hand.

https://t.co/cg1xoqpoGS

#flutter #vibecoding

[Draw.app @drawd_app]

@SHUBHAM84499771 Day 12 and already shipping - solid momentum. The on-call constraint probably forces you to be really efficient with your prompting time. Do you plan out the screens before coding or just dive in?

[Draw.app @drawd_app]

@imrishabsharma The real edge is input quality. Most prompts miss navigation flow and edge cases - that's where devs who structure their specs before prompting pull ahead. What does your workflow look like?

[Draw.app @drawd_app]

@devontrails Six tabs is the breaking point where you build your own tool. Did you start from a visual plan or go straight into prompting? Curious how you structured the navigation for that many views.

[Draw.app @drawd_app]

@Jiezi76371912 Love the concept of digital products mimicking the physical world! What made you pick iOS for V1 - and what was the hardest screen to get right with Claude Code?

[Draw.app @drawd_app]

Show HN: Drawd – browser-native app flow designer that generates AI build instructions

Upload screens → draw hotspots → connect screens → export markdown for LLMs

No sign-up. No cloud. Saves to a .drawd file.

https://t.co/R68WkPGukd

#buildinpublic #indiedev

[Draw.app @drawd_app]

@Gordey0072 It's becoming easy to spot right? The generic gradients, the same hero layouts. I think the missing piece is that most people skip the design and nav planning phase and just prompt straight to code. What patterns do you notice most?

[Draw.app @drawd_app]

@ashutoshkmrr The day job + vibe coding side hustle split is relatable. Curious - what are you building on the side? Do you find the context switching between structured work and freeform AI coding hard?

[Draw.app @drawd_app]

@Aizentic The worst timing every time. Breaking the task into smaller scoped prompts with clear navigation context helps stay within limits. What were you building when it hit?

[Draw.app @drawd_app]

@aykolho Both still have a place imo. Nocode is great for standard patterns, but vibecoding lets you go way more custom. The real shift I see is in input quality - structured specs vs vague prompts make a huge difference in what AI actually builds. Have you tried both approaches?

[Draw.app @drawd_app]

@NitinGavhane_ Solid repo. The "it feels like magic" part fades fast when the AI misunderstands your structure. The ceiling for vibe coding is really how precisely you can describe the app's navigation and state upfront.

[Draw.app @drawd_app]

@aditya_elevate The filter variations look great — what's been the trickiest part of Crest to get right so far?

[Draw.app @drawd_app]

@trekhleb The compare feature looks clean — did this feel like one of those "describe it and Claude just builds it" moments, or did the layout take a lot of iteration to get right?

[Draw.app @drawd_app]

Before: sketch on paper -> spend 30 min typing navigation prompts -> AI misunderstands -> redo

After: upload screens -> draw hotspots -> connect flows -> export ZIP -> AI builds it right

https://t.co/cg1xoqpoGS

#vibecoding #buildinpublic

[Draw.app @drawd_app]

@samsonA535 Nice to meet you

[Draw.app @drawd_app]

@ilan_hertz That question hits different when you realize the main bottleneck isn't the AI anymore — it's how clearly you can describe what you're building before you start.

[Draw.app @drawd_app]

@ashir_designs @GoogleAIStudio @GeminiApp Geopolitics + economics through a game — that's ambitious. What's the hardest part to explain to the AI so far, the game logic or the UI flows?