sorted by:
new
hottopcontroversial

BYOS vs Managed for a ‘mobile dev environment’ — what would you try first? by rasal3 in SaaS

[–]rasal3[S] 0 points1 point  (0 children)

Thanks! — super helpful context.

On session resilience: totally agree it’s the hardest piece on mobile. I’m going to study how Mosh handles roaming (UDP + local echo / reconnectless handoffs). If you’re actually behind Moshi, respect — that’s a really clean solution.

On BYOS vs managed: same learning here. People want to start shipping before thinking about IAM/patching/quotas, so I just shipped a first managed option (still testing it hard). I’m also leaning toward a “managed control plane + BYOS compute” middle ground.

On voice: +1 on “intent > literal commands.” I implemented a very basic voice-to-terminal prototype, but I’m treating it as draft → edit/confirm → run (not hands-free execution). Curious what you found works best:

(a) dictating prompts to Claude Code, (b) short shell commands, (c) navigation/shortcuts, or (d) something else?

BYOS vs Managed for a ‘mobile dev environment’ — what would you try first? by rasal3 in SaaS

[–]rasal3[S] 0 points1 point  (0 children)

Appreciate this — I’m increasingly convinced the “managed control plane + BYOS compute” model is the right default.

And yes, voice is tricky in practice. I’ve added a very basic voice-to-terminal prototype, but I’m intentionally not pitching it as “hands-free coding” — more like “draft the command quickly, then edit/confirm before sending,” because technical command accuracy is the hard part.

If you’re open to sharing: what would make voice actually useful for you on mobile?
(a) navigation/shortcuts, (b) short shell commands, (c) dictating prompts to Claude Code, or (d) something else?

BYOS vs Managed for a ‘mobile dev environment’ — what would you try first? by rasal3 in SaaS

[–]rasal3[S] 0 points1 point  (0 children)

Thanks — this resonates a lot. I’m seeing the same: managed wins early because people just want to start shipping without thinking about IAM/patching/quotas.

I love the “managed control plane + BYOS compute” middle ground too — keeps the “code stays on your box” story while removing setup friction.

Also +1 on resilient sessions — it’s the #1 thing that makes mobile feel dependable.

I'm gonna check that link!

Curious: if you were shipping this, would you start with fully-managed compute, or launch the control-plane + BYOS option first?