Practice feedback on GetAdvice 🔎

GetAdvice is a real public app — MILO’s friendly face out in the world. Your job in this folder is simple: use it, write down what you notice, and then review your own note.

You are practicing a skill every builder needs. A good report tells someone else exactly what you did, what you expected, and what happened, so they could see the same thing. Think of it like a taste-tester for food: you try a bite and say “this needs a little more salt,” with enough detail that the cook can find the pot.

New to this and want the full walkthrough first? Read lessons/07-giving-good-feedback.md. This page is the short version for when you are ready to go.

How to write a note

  1. Open GetAdvice at getadviceapp.com. There is also an iPhone app under the same name. Use it like a curious first-time visitor. Try a real question. Notice what feels clear and what feels stuck.
  2. Open the template: feedback-getadvice/feedback-template.md. A template is a fill-in-the-blanks form, like a worksheet.
  3. Copy it into a new file in this notes/ folder. Name it after the day and the issue, for example notes/2026-10-26-button-hard-to-find.md.
  4. One note per issue or idea. If you spot three things, that is three separate notes.
  5. Fill in the blanks with clear, simple steps. Pretend you are telling a friend exactly what you did, in order, so they could do the same thing and see the same result.
  6. Add a screenshot whenever you can. A screenshot is a picture of your screen.

The two notes already in notes/ are worked examples shipped with the course. Read them. Leave them as they are. Your work is a new file beside them.

If you cannot open GetAdvice, practice on your own project from my-projects/ instead. Say that at the top of the note. The skill is the same.

If you get stuck on the wording, ask MILO to help you say it clearly. You still supply the facts.

Review your own note

Before you call it done, read the note once more and check each box. This review is yours. Nothing in this repo scores it for you.

  • A stranger could follow what I was doing and land on the same screen.
  • What I expected and what actually happened are two different sentences.
  • The note names the screen and the device.
  • There is one issue in this note, not a bundle of them.
  • I could explain, out loud, why it matters to a new person.

Small ideas are very welcome

You do not have to find a big broken thing. Small polish ideas count just as much. For example:

  • Wording that was confusing or hard to read.
  • Spacing that looked cramped or messy.
  • A spot that felt slow.
  • Anything that just felt a little off.

If it caught your eye, it is worth a note.

Showing your work

Keep the note in your copy of the repo. That file is the hand-in.

If you have an instructor, show them the file (or commit it and send the link). Lessons later in the course also use a course inbox, milo@jmautomated.com, when they ask you to send a short summary. You can attach this note to that summary if you want to.

One last thing 💛

Finding problems is helping, not criticizing. A clear note makes the next version better for the people who use the app. There are no silly reports here.

Ready? Grab the template and start: feedback-getadvice/feedback-template.md

🎉 Nice work — you know how to test an app and turn what you notice into a clear, kind note.

Want a refresher on writing great feedback first? Head to lessons/07-giving-good-feedback.md.