Does anyone else find that building mobile apps with no-code tools still involves a significant amount of complexity, particularly during the App Store submission stage?
Does anyone else find that building mobile apps with no-code tools still involves a significant amount of complexity, particularly during the App Store submission stage?. Does anyone else find that building mobile apps w
Comment on: Launch HN: Prized (YC S26) – Let non-engineer staff build secure internal tools
Closest comp. I'd argue the "AI builds the app part" is fast becoming table stakes. The unsolved problem is what happens after the app exists and that's what we actually built. Anyone in the org can fork a coworker's tool and rebind it to their own data scope. Enforcement also happens at a different layer. From what we've gathered, Superblocks controls who can run an app and bakes guardrails in when the app is generated, but every app still queries through a shared database credential. On our side, each tool gets its own database role that can only see its own data, and credentials live in a p
Comment on: Where I'm at with AI
> But I think we're still a long way off non-technical people being able to develop applications.I'm surprised I haven't seen anyone do a case study, having truly non-technical people build apps with these tools. Take a few moderately tech-savvy (can use MS office up to doing basic stuff in excel, understands a filesystem) people who work white collar jobs. Give them a one or two-day crash course on how Claude Code works. See what is the most complicated app which they can develop that is reasonably stable and secure.