Feedback Note

Worked example. This note ships with the course so you can see a finished report. Read it. Leave it unchanged. Your own notes are new files in this same folder.

Title: App froze when asking coding questions

What I was doing: I asked GetAdvice questions about code, which apps I could use for coding, what AI model it is, and when it was last updated.

What I expected: Clear, correct answers to my questions.

What actually happened: The app froze / got stuck while responding.

Where (screen or page): Chat / conversation screen

Device: iPhone 17 Pro Max

Screenshot: none

How much it bugged me: big

Why it matters (optional): If it freezes on normal questions, it makes the app feel unreliable for any user who tries it.

Idea to fix (optional):

Repro

  1. Open GetAdvice on the iPhone and go to the chat/conversation screen.
  2. Type a normal question, for example: “What AI model are you?”
  3. Send the message and watch the screen.
  4. Type a second question, for example: “When was your last update?”, and send it too.

Expected: The app shows some kind of visible feedback right after sending (a reply, or at least a “thinking” indicator) within a few seconds.

Actual: After sending, the screen shows nothing new — no reply, no loading indicator, no visible change — and stops responding to taps, so it looks and feels frozen.

Re-tested today (2026-07-02): same result. Asking “what model are you?” and “when was your last update?” both produced the same silent, unresponsive screen with no loading indicator before anything appeared.

Hypothesis

I think this happens because GetAdvice is waiting on a response (most likely a network call to an AI model) without showing any loading state while it waits. With no visual feedback, a normal wait looks identical to a frozen app, even though a request may still be running in the background. This is probably worse for questions like “what model are you?” or “when was your last update?” because those likely aren’t answered from a quick pre-written script — they may go through the same slower process as every other question, or have no clear answer source at all. If the app also doesn’t disable or re-enable the input correctly during that wait, or has no timeout/fallback for a slow response, the screen can end up stuck with nothing for the user to do but wait or force-close the app.