2026.11.10

5 tips for app development with dots

Switch to Codex before using it in the desktop app, sort out requirements in advance, automate from Issue to implementation with scheduled runs, have it operate another PC to implement, and don't hand off tasks in parallel while requirements aren't settled.

I got lots of tips for doing app development with dots, so I’m sharing them!

① In the desktop app, switch to Codex before using it It runs as a Codex thread instead of a regular chat, so accuracy might improve. In regular ChatGPT, it runs as Work.

② Sort out requirements in advance Rather than dumping 0→100 on dots, it seems better to break things down into tickets and an execution plan first. Doing requirements definition together with dots is effective, but instead of having it implement everything straight away, cutting the work into tickets first and handing it to Codex ticket by ticket seems like a way to delegate with peace of mind.

③ Automate from Issue to implementation with scheduled runs Apparently you can also have dots regularly monitor whether Issues have come up and then hand off the implementation as is. You can run it so that humans only check the finished PRs and previews.

④ Have it operate another PC to implement dots has its own cloud PC, and it can also launch Codex tasks on connected PCs. You can have it operate a PC other than the one in front of you and implement there, so I recommend it. You can also run environment-dependent tests.

⑤ Don’t hand off tasks in parallel while requirements aren’t settled If requirements aren’t decided when delegating tasks from dots → Codex, each one ends up doing duplicate implementation. Things also tend to get lost in communication when specs change, so avoid it.

#DevDayCommunity

https://x.com/suna_gaku/status/2108189942908420166