Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

I Used an AI Assistant on My Phone as a Dev Tool for a Month. Here’s the Honest Verdict.

说明与用途

移动 AI 助手有助于调试、阅读代码和编写工单,但不适合编写代码、维护上下文和建立信任。

问题

Can a mobile AI assistant serve as a practical development tool outside a desktop environment?

结果

The AI assistant improved on‑the‑go debugging, code comprehension, and drafting, saving about 20 minutes per day, but remained inadequate for writing code longer than ~30 lines, maintaining full codebase context, and ensuring trust in generated code.

工作流

  • 1. Use phone to explain bugs aloud to the AI assistant while walking.
  • 2. Paste a function into the assistant and ask for a step‑by‑step explanation.
  • 3. Dictate a rough idea for a ticket or PR description and receive a clean draft.
  • 4. Review and tidy drafts on a laptop before finalizing.

证据

Rubber‑ducking on the go. Nine times out of ten, the bug I'm stuck on isn't a typing problem. It's a thinking problem. Explaining it out loud to an assistant on a walk solved more issues than I'd like to admit.

来源

Reading unfamiliar code. Pasting a gnarly function and asking "what does this actually do, step by step" is genuinely useful on a small screen.

来源

Drafting tickets and PR descriptions. I'd dictate the rough idea, get a clean draft back, and tidy it later at my desk. Saved me maybe 20 minutes a day.

来源

Writing real code. Anything longer than ~30 lines on a phone is still miserable, AI or not. Reviewing a diff on a 6-inch screen is how bugs get shipped.

来源

Context. The assistant doesn't know your codebase unless you feed it. On mobile, feeding it is the hard part.

来源

Trust. It's confidently wrong sometimes. Rule of thumb: never merge anything you couldn't explain to a colleague.

来源

  • 记录日期: 2026-10-11T07:41:24.070Z