Original Summary

My latest release is DeskRhythm, an app that tells you when to switch between sitting, standing and moving during the workday. It's on the web and, as of this week, on iPhone. Android is in progress. It's the newest of several apps from my small studio, My Next Studio, with more on the way. Most of them were built the same way, with Build Studio, a workflow tool I made and open-sourced. Instead of prompting my way forward change by change, AI agents play a small product team: a PM drafts a short spec for one small feature, and asks me only the questions that change the product reviewers (architecture, UX, brand, security, QA) check the spec against the product vision before anything is built a developer agent implements it in its own git worktree, with tests QA and code review check the result, and I approve or send it back at the gates For DeskRhythm that means a React web app, a SwiftUI iOS app and a Kotlin Android app in progress, all from one repo. What I've learned across the apps: the agents are good at building, but the useful part is the structure. Small specs I can actually read, a written vision they get checked against, and me deciding at the points that matter. When a step shows the vision is wrong, changing the vision is an explicit decision instead of silent drift. DeskRhythm: https://deskrhythm.com (the web version is free, no account) iPhone: https://apps.apple.com/app/id6780625435 All the apps: https://mynextstudio.com Demos of the apps and the build process: https://www.youtube.com/@MyNextStudio Build Studio (Apache 2.0): https://github.com/My-Next-Studio/build-studio Happy to go into any part of it: the workflow, what broke, or what I'd do differently.   submitted by   /u/Independent-Fail9636 [link]   [comments]

  • 情报分类：硬件与数码
  • 分类依据：内容涉及硬件、数码产品或通信卡
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/26 17:50:01