Gin — MIT App Inventor

127 sessions · MIT App Inventor · Wednesdays 3:30–5:00pm · 90 minutes each · 18 Nov 2026 – 18 Apr 2029 · 190.5 hours total.

Built on what he already knows: resistor colour codes and Ohm’s Law (V = I × R). All block-based, Designer + Blocks, no text programming. MIT App Inventor is Rica’s exploration with Gin, not a CIY-assigned track — no CIY level is claimed for it. Sessions 1–8 match the 8-session plan already made for him.

Showing 127 of 127 sessions

Session 1First app — Designer, button + label, test with CompanionWed 18 Nov 2026
Wed 18 Nov 2026 | Phase 1 — Foundations & Electronics Tools

Date: Wed 18 Nov 2026 | Phase: Phase 1 — Foundations & Electronics Tools Learning objective: Gin can build his first working app in MIT App Inventor: a button that changes a label, and test it live on a phone with the Companion. Components: Label1, Text "Press the button!", FontSize 24, FontBold true; Button1, Text "Show Ohm's Law", FontSize 18, BackgroundColor Blue; Button2, Text "Clear", FontSize 18; Label2, Text "", FontSize 20, TextColor Dark Gray; HorizontalArrangement1 (holds Button1 + Button2). Step-by-step build:

1) Designer setup: Open ai2.appinventor.mit.edu, start a new project named GinFirstApp. Drag Label1 to the top of Screen1, then Button1 and Button2 into HorizontalArrangement1 below it, then Label2 underneath. Set the texts and sizes above; set Screen1 Title to "Gin — First App".

2) Blocks setup: Switch to Blocks. Snap when Button1.Click → set Label2.Text to "V = I × R" (use a text block). Snap when Button2.Click → set Label2.Text to "" (empty text block). No variables yet.

3) Test: Connect → AI Companion, scan the QR code with the MIT AI2 Companion app on the phone. Tap Button1 — Label2 must show "V = I × R". Tap Button2 — it clears. If the Companion asks, allow it and wait for "Connected".

90-minute timing: 0–10 plan/sketch — draw the screen on paper (label on top, two buttons, answer label); 10–20 demo — Rica shows a finished first app and the Companion connection; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test on phone, fix text/colour; 80–90 share — show Ray and Run, screenshot the phone. Test checklist: Companion connects and shows the app; Button1 shows "V = I × R"; Button2 clears it; text is big enough to read. Common bug: tapping the button does nothing — fix: check the block is when Button1.Click (not Button2) and that the Companion is connected (re-scan the QR code). Success check: Gin's button changes the label on the real phone, and he can explain Designer vs Blocks in one sentence. Homework: Change Button1's text to "Show a fact" and make Label2 show one electronics fact, e.g. "Resistors limit current".

Session 2Tap counter + variables — score, reset, best scoreWed 25 Nov 2026
Wed 25 Nov 2026 | Phase 1 — Foundations & Electronics Tools

Date: Wed 25 Nov 2026 | Phase: Phase 1 — Foundations & Electronics Tools Learning objective: Gin can use a global variable to count taps, show the score, reset it, and keep a best score. Components: Label1, Text "Tap the resistor!", FontSize 24; Button1, Text "TAP!", FontSize 28, BackgroundColor Orange; LabelScore, Text "Score: 0", FontSize 22; LabelBest, Text "Best: 0", FontSize 20; ButtonReset, Text "Reset", FontSize 18. Step-by-step build:

1) Designer setup: New project GinTapCounter (or copy Session 1 and rename). Add the components above in order: Label1, Button1, LabelScore, LabelBest, ButtonReset.

2) Blocks setup: Create initialize global score to 0 and initialize global best to 0. Snap when Button1.Click → set global score to (get global score + 1) (math + block, number 1) → set LabelScore.Text to join "Score: " + get global score (text join block) → if get global score > get global best then set global best to get global score → set LabelBest.Text to join "Best: " + get global best. Snap when ButtonReset.Click → set global score to 0 → set LabelScore.Text to "Score: 0" (leave Best unchanged).

3) Test: Companion — tap Button1 ten times fast; Score must read 10, Best 10. Tap Reset — Score 0, Best stays 10. Tap 3 more times — Score 3, Best still 10.

90-minute timing: 0–10 plan/sketch — sketch the counter screen, predict what a variable does; 10–20 demo — Rica shows a counter and changes the variable live; 20–65 build — Designer + variable blocks; 65–80 test & fix — tap-test, check Best never drops; 80–90 share — who can tap fastest in 10 seconds? Screenshot. Test checklist: Each tap adds exactly 1; Reset clears Score but not Best; Best only goes up. Common bug: Score jumps by 2 or resets Best too — fix: check there is only one + 1 block, and Reset sets only score, not best. Success check: Gin can explain "a variable remembers a number" and his Best score survives a reset. Homework: Add a second button "Tap ×2" that adds 2 per tap, and test it.

Session 3Ohm's Law calculator — inputs, maths blocks, V = I × RWed 2 Dec 2026
Wed 2 Dec 2026 | Phase 1 — Foundations & Electronics Tools

Date: Wed 2 Dec 2026 | Phase: Phase 1 — Foundations & Electronics Tools Learning objective: Gin can build a calculator that takes current (I) and resistance (R) and computes voltage with V = I × R, using maths blocks. Components: LabelTitle, Text "Ohm's Law: V = I × R", FontSize 22, FontBold true; LabelI, Text "Current I (amps):", FontSize 18; TextBoxI, Hint "Enter current, e.g. 2", NumbersOnly true; LabelR, Text "Resistance R (ohms):", FontSize 18; TextBoxR, Hint "Enter resistance, e.g. 10", NumbersOnly true; ButtonCalc, Text "Calculate V", FontSize 20, BackgroundColor Green; LabelAnswer, Text "V = ?", FontSize 24, FontBold true. Step-by-step build:

1) Designer setup: New project GinOhmsLaw. Add components in order above; set TextBoxI and TextBoxR to NumbersOnly so only digits can be typed.

2) Blocks setup: Snap when ButtonCalc.Click → set LabelAnswer.Text to join "V = " + (get TextBoxI.Text × get TextBoxR.Text) + " V" — use a math × block; because TextBox text is text, wrap each with nothing extra (App Inventor converts numbers), or use math blocks directly on the TextBox values. Example check: I = 2, R = 10 → V = 20, so LabelAnswer shows "V = 20 V". Stretch: add a second button "Calculate I" using set LabelAnswer.Text to join "I = " + (V ÷ R) with two more TextBoxes — only if time allows.

3) Test: Companion — type 2 and 10, tap Calculate, expect "V = 20 V". Try I = 0.5, R = 100 → "V = 50 V".

90-minute timing: 0–10 plan/sketch — write V = I × R on paper, pick test numbers; 10–20 demo — Rica calculates 2 × 10 = 20 on paper, then in the app; 20–65 build — Designer + maths blocks; 65–80 test & fix — test 2–3 number pairs; 80–90 share — Gin quizzes Rica: "I = 3, R = 4 — what does your app say?" Screenshot. Test checklist: 2 and 10 give 20 V; 0.5 and 100 give 50 V; empty boxes do not crash the app (shows 0 or blank). Common bug: answer shows "210" instead of 20 — fix: the values were joined as text, not multiplied; make sure the × maths block (not join) does the calculation. Success check: Gin's app correctly calculates V for any I and R he types. Homework: Add a label under the answer that shows the formula used, e.g. "2 A × 10 Ω = 20 V".

Session 4Resistor colour-code decoder — lists, choices, lookupWed 9 Dec 2026
Wed 9 Dec 2026 | Phase 1 — Foundations & Electronics Tools

Date: Wed 9 Dec 2026 | Phase: Phase 1 — Foundations & Electronics Tools Learning objective: Gin can build a decoder that turns two colour choices into a resistance value, using lists and lookup logic. Components: LabelTitle, Text "Resistor Decoder", FontSize 22, FontBold true; SpinnerBand1, ElementsFromString "Black,Brown,Red,Orange,Yellow,Green,Blue,Violet,Grey,White"; SpinnerBand2, same list; LabelPick, Text "Pick two colours", FontSize 18; ButtonDecode, Text "Decode", FontSize 20, BackgroundColor Blue; LabelAnswer, Text "Resistance = ?", FontSize 22, FontBold true; LabelExample, Text "Brown-Black-Red = 1,000 Ω", FontSize 16. Step-by-step build:

1) Designer setup: New project GinResistorDecoder. Add the components above. A Spinner is a drop-down list — set both Spinners' ElementsFromString to the 10-colour list. Set SpinnerBand1 and SpinnerBand2 Prompt to "Band 1" / "Band 2".

2) Blocks setup: Create initialize global colourValues to make a list [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] (Black=0 … White=9, in the same order as the Spinner list). Snap when ButtonDecode.Click → set global digit1 to select list item (list get global colourValues, index SpinnerBand1.SelectionIndex) → same for digit2 with SpinnerBand2 → set LabelAnswer.Text to join "Resistance = " + ((get global digit1 × 10 + get global digit2) × 100) + " Ω" — the ×100 is the Red third band (multiplier 100) for this first version. Example: Brown (1), Black (0) → (1×10+0)×100 = 1,000 Ω. Add a if SpinnerBand1.Selection = "" then set LabelAnswer.Text to "Pick both colours first" guard at the top.

3) Test: Companion — pick Brown + Black, tap Decode, expect "Resistance = 1000 Ω". Try Red + Red → (2×10+2)×100 = 2,200 Ω.

90-minute timing: 0–10 plan/sketch — colour-code table on paper (Black 0 … White 9); 10–20 demo — Rica decodes Brown-Black-Red by hand, then in the app; 20–65 build — Spinners + list + lookup blocks; 65–80 test & fix — test 3 colour pairs; 80–90 share — Gin decodes a real resistor from his electronics kit. Screenshot. Test checklist: Brown + Black = 1,000 Ω; Red + Red = 2,200 Ω; tapping Decode with no colour picked shows the reminder, not a crash. Common bug: answer is wrong by one colour — fix: check the list order matches the Spinner order exactly (Black first = 0). Success check: Gin's app decodes any two-band pair correctly for the Red multiplier, and he can say what a list index is. Homework: Write down the 10 colours and their numbers from memory, then check against the app.

Session 5Electronics quiz app — questions, score, feedbackWed 16 Dec 2026
Wed 16 Dec 2026 | Phase 1 — Foundations & Electronics Tools

Date: Wed 16 Dec 2026 | Phase: Phase 1 — Foundations & Electronics Tools Learning objective: Gin can build a 5-question electronics quiz that checks answers, gives feedback, and keeps score. Components: LabelQuestion, Text "Question 1", FontSize 22, FontBold true; ButtonA, Text "A", FontSize 18; ButtonB, Text "B", FontSize 18; ButtonC, Text "C", FontSize 18; ButtonD, Text "D", FontSize 18; LabelFeedback, Text "", FontSize 20; LabelScore, Text "Score: 0 / 5", FontSize 20; ButtonNext, Text "Next question", FontSize 18, BackgroundColor Green. Step-by-step build:

1) Designer setup: New project GinElectronicsQuiz. Add LabelQuestion, four answer Buttons (A–D) stacked vertically, LabelFeedback, LabelScore, ButtonNext.

2) Blocks setup: Create initialize global questions to make a list ["What does V stand for in Ohm's Law?", "What colour is 1 in resistor codes?", "What is the unit of resistance?", "In series, total resistance is…?", "What does a resistor do?"], initialize global answers to make a list ["Voltage", "Brown", "Ohm", "The sum of all resistors", "Limits current"], initialize global choices to make a list of 5 sub-lists of 4 options each (correct answer placed in a different position each time), initialize global qIndex to 1, initialize global score to 0. Make a procedure showQuestion: set LabelQuestion.Text to select list item (get global questions, get global qIndex) and set ButtonA–D Text from the matching choices sub-list. Snap each answer button: when ButtonA.Click → if ButtonA.Text = select list item (get global answers, get global qIndex) then set global score to get global score + 1, set LabelFeedback.Text to "Correct!" else set LabelFeedback.Text to join "Wrong — the answer is " + correct answer → update LabelScore. Snap when ButtonNext.Click → set global qIndex to get global qIndex + 1 → if get global qIndex > 5 then set LabelQuestion.Text to join "Quiz done! Score: " + get global score + " / 5" else call showQuestion and clear LabelFeedback.

3) Test: Companion — play all 5 questions; a correct tap says "Correct!" and adds 1; a wrong tap shows the right answer; after Q5 the final score shows.

90-minute timing: 0–10 plan/sketch — write the 5 questions and answers on paper first; 10–20 demo — Rica plays a 2-question mini-quiz; 20–65 build — lists + answer-checking blocks; 65–80 test & fix — play the whole quiz twice; 80–90 share — Ray and Run try the quiz. Screenshot. Test checklist: All 5 questions appear in order; correct answers score 1 each; wrong answers show the correct one; Q5 ends with a final score. Common bug: every answer counts as wrong — fix: check the comparison uses the same list item (same qIndex) in answers and that Button Text matches it exactly, including capital letters. Success check: Gin can play his full 5-question quiz start to finish with correct scoring. Homework: Add a 6th question of his own, with 4 choices, to the lists.

Session 6Multi-screen app — component library, navigationWed 23 Dec 2026
Wed 23 Dec 2026 | Phase 1 — Foundations & Electronics Tools

Date: Wed 23 Dec 2026 | Phase: Phase 1 — Foundations & Electronics Tools Learning objective: Gin can build a multi-screen app with a home screen that opens three tool screens and a working Back button on each. Components: Screen1 (Home): LabelTitle "Gin's Electronics Lab", FontSize 26; ButtonCalc "Ohm's Law Calculator"; ButtonDecoder "Resistor Decoder"; ButtonQuiz "Electronics Quiz"; Screen2 (Calculator): Label "Ohm's Law", TextBoxI, TextBoxR, ButtonCalc, LabelAnswer, ButtonBack "← Home"; Screen3 (Decoder): SpinnerBand1, SpinnerBand2, ButtonDecode, LabelAnswer, ButtonBack; Screen4 (Quiz): LabelQuestion, ButtonA–D, LabelFeedback, ButtonBack. (Reuse the blocks from Sessions 3–5 inside Screens 2–4.) Step-by-step build:

1) Designer setup: New project GinElectronicsLab. On Screen1 add the title and three navigation buttons. Click "Add Screen…" and create Screen2, Screen3, Screen4; on each, add that tool's components from the earlier sessions plus a ButtonBack at the bottom.

2) Blocks setup: On Screen1: when ButtonCalc.Click → open another screen screenName "Screen2", same for ButtonDecoder → "Screen3", ButtonQuiz → "Screen4". On each of Screens 2–4: when ButtonBack.Click → close screen (returns to Home). Copy the working blocks from Sessions 3, 4 and 5 into Screens 2, 3 and 4 respectively — do not rebuild from scratch if the earlier projects can be copied.

3) Test: Companion — from Home, open each screen, use the tool once, tap Back, and confirm you land on Home each time.

90-minute timing: 0–10 plan/sketch — draw 4 boxes (Home + 3 tools) with arrows; 10–20 demo — Rica navigates a sample multi-screen app; 20–65 build — add screens, copy tool blocks in, wire navigation; 65–80 test & fix — open every screen and go Back; 80–90 share — show the full lab to Ray and Run. Screenshot each screen. Test checklist: All three Home buttons open the right screen; every Back button returns Home; each tool still works on its own screen. Common bug: a button opens the wrong screen or nothing happens — fix: check the screenName text matches exactly ("Screen2", capital S, no spaces) and that the button's event is on Screen1's Blocks, not another screen's. Success check: Gin can navigate Home → any tool → Home without getting stuck. Homework: Add a 4th Home button "About" that opens a new Screen5 with one label about himself as the maker.

Session 7Sensor app — accelerometer / sound, live readingWed 30 Dec 2026
Wed 30 Dec 2026 | Phase 1 — Foundations & Electronics Tools

Date: Wed 30 Dec 2026 | Phase: Phase 1 — Foundations & Electronics Tools Learning objective: Gin can build an app that reads the phone's accelerometer live and shows X, Y and Z values that change as he tilts the phone. Components: AccelerometerSensor1 (non-visible); LabelTitle, Text "Tilt Sensor", FontSize 24, FontBold true; LabelX, Text "X: 0", FontSize 22; LabelY, Text "Y: 0", FontSize 22; LabelZ, Text "Z: 0", FontSize 22; LabelTilt, Text "Hold the phone flat", FontSize 20; ButtonFreeze, Text "Freeze reading", FontSize 18; SoundRecorder1 (non-visible, only if the phone supports it — optional stretch, see step 3). Step-by-step build:

1) Designer setup: New project GinSensorApp. Drag AccelerometerSensor1 from Sensors into the viewer (it sits below the screen, non-visible). Add the labels and ButtonFreeze. Set AccelerometerSensor1 MinimumInterval to 100.

2) Blocks setup: Create initialize global frozen to false. Snap when AccelerometerSensor1.AccelerationChanged → if not get global frozen then set LabelX.Text to join "X: " + get xAccel → same for Y (get yAccel) and Z (get zAccel) → if get xAccel > 5 then set LabelTilt.Text to "Tilted right!" else if get xAccel < -5 then set LabelTilt.Text to "Tilted left!" else if get yAccel > 5 then set LabelTilt.Text to "Tilted forward!" else set LabelTilt.Text to "Hold the phone flat". Snap when ButtonFreeze.Click → set global frozen to not get global frozen → if get global frozen then set ButtonFreeze.Text to "Unfreeze" else set ButtonFreeze.Text to "Freeze reading".

3) Test: Companion — hold the phone flat: Z should read near 9.8, X and Y near 0. Tilt right: X rises and LabelTilt says "Tilted right!". Tap Freeze: numbers stop changing. Stretch only if the sensor works well: add a SoundRecorder1 button that records 3 seconds and plays it back.

90-minute timing: 0–10 plan/sketch — draw the phone, label X/Y/Z arrows; 10–20 demo — Rica tilts her phone and the numbers move; 20–65 build — sensor + live-reading blocks; 65–80 test & fix — tilt in all four directions, test Freeze; 80–90 share — Gin demonstrates tilt to Ray and Run. Screenshot. Test checklist: Flat phone shows Z ≈ 9.8; tilting changes X/Y and the Tilt label; Freeze stops updates and Unfreeze restarts them. Common bug: numbers never change — fix: check the event is AccelerationChanged (not a button event), the Companion is connected, and test on the real phone, not the emulator (the emulator has no real accelerometer). Success check: Gin can tilt the phone and explain which number (X, Y or Z) moved and why. Homework: Write down the X/Y/Z readings for flat, tilted right, and tilted forward, and bring the numbers next week.

Session 8Capstone 1 — Resistor Helper / Circuit Calculator, showcaseWed 6 Jan 2027
Wed 6 Jan 2027 | Phase 1 — Foundations & Electronics Tools

Date: Wed 6 Jan 2027 | Phase: Phase 1 — Foundations & Electronics Tools Learning objective: Gin can combine his calculator, decoder and quiz into one polished Resistor Helper app and present it in a 2-minute showcase. Components: Screen1 (Home): LabelTitle "Resistor Helper", FontSize 26; ButtonCalc "Ohm's Law"; ButtonDecoder "Resistor Decoder"; ButtonQuiz "Quick Quiz"; ButtonAbout "About"; Screen2 Calculator (from Session 3 + a series-total row: TextBoxR1, TextBoxR2, ButtonSeries, LabelSeries "Total = ?"); Screen3 Decoder (Session 4); Screen4 Quiz (Session 5, 5 questions); each tool screen has ButtonBack "← Home". Step-by-step build:

1) Designer setup: Copy the Session 6 project and rename it GinResistorHelper. Check every screen: fix titles, font sizes and button colours so all screens look like one app (same blue header style). On Screen2 add the series row: Label "Series total: R1 + R2", TextBoxR1, TextBoxR2, ButtonSeries, LabelSeries.

2) Blocks setup: Keep all Session 6 navigation and tool blocks. Add on Screen2: when ButtonSeries.Click → set LabelSeries.Text to join "Total = " + (get TextBoxR1.Text + get TextBoxR2.Text) + " Ω" — example R1 = 100, R2 = 200 → "Total = 300 Ω". Fix any bug found in testing (e.g. empty-box crash: add if TextBoxR1.Text = "" then set LabelSeries.Text to "Enter both resistors"). Add an About screen (Screen5): one label "Made by Gin, CIY Club — Resistor Helper helps you decode resistors and use Ohm's Law."

3) Test: Companion — full run-through: Home → Calculator (V = 20 for I = 2, R = 10) → Back → Decoder (Brown-Black = 1,000 Ω) → Back → Quiz (play 2 questions) → Back → Series (100 + 200 = 300 Ω). Rehearse a 2-minute talk: what the app does, one demo, one thing he would add next.

90-minute timing: 0–10 plan/sketch — list what is finished vs what still needs fixing; 10–20 demo — Rica shows a polished example and a 2-minute talk; 20–65 build — polish + series total + About screen; 65–80 test & fix — full run-through, fix every bug found; 80–90 share — Gin presents Resistor Helper to Ray, Run and Rica (2 minutes). Screenshot all screens. Test checklist: Every screen opens and returns Home; calculator, decoder, quiz and series total all give correct answers; no screen crashes on empty input. Common bug: one tool broke when copied into the capstone — fix: check that component names match the blocks (e.g. TextBoxR1 exists on Screen2 and the block says TextBoxR1, not TextBoxR). Success check: Gin presents a working, polished Resistor Helper with no crashes, and can name one feature he wants to add next. Homework: Save/export the .aia file (Projects → Export selected project) and write down three ideas for Capstone 2.

Session 9Reaction game — tap fast, timer, best timeWed 13 Jan 2027
Wed 13 Jan 2027 | Phase 2 — Games & Interaction

Date: Wed 13 Jan 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a reaction game where a button appears after a random wait, the player taps it fast, and the app shows the reaction time and best time. Components: LabelTitle, Text "Reaction Game", FontSize 24, FontBold true; ButtonTap, Text "Wait for green…", FontSize 22, BackgroundColor Red, Enabled false; ButtonStart, Text "Start", FontSize 20, BackgroundColor Green; LabelTime, Text "Time: —", FontSize 22; LabelBest, Text "Best: —", FontSize 20; Clock1, TimerEnabled false, TimerInterval 100. Step-by-step build:

1) Designer setup: New project GinReactionGame. Add components above. Set Clock1 TimerEnabled false at start.

2) Blocks setup: Create initialize global startTime to 0, initialize global bestTime to 0, initialize global waiting to false. Snap when ButtonStart.Click → set ButtonStart.Enabled to false → set ButtonTap.Text to "Wait…" → set ButtonTap.BackgroundColor to Red → set Clock1.TimerInterval to random integer from 1000 to 3000 → set Clock1.TimerEnabled to true. Snap when Clock1.Timer → set Clock1.TimerEnabled to false → set ButtonTap.BackgroundColor to Green → set ButtonTap.Text to "TAP NOW!" → set ButtonTap.Enabled to true → set global startTime to Clock1.SystemTime. Snap when ButtonTap.Click → if get global waiting = false and ButtonTap.BackgroundColor = Green then set global reaction to (Clock1.SystemTime - get global startTime) → set LabelTime.Text to join "Time: " + get global reaction + " ms" → if get global bestTime = 0 or get global reaction < get global bestTime then set global bestTime to get global reaction → set LabelBest.Text to join "Best: " + get global bestTime + " ms" → set ButtonTap.Enabled to false → set ButtonStart.Enabled to true → else (tapped too early, while red) set LabelTime.Text to "Too soon! Press Start again." → set Clock1.TimerEnabled to false → set ButtonStart.Enabled to true.

3) Test: Companion — tap Start, wait for green, tap fast; expect a time in ms (e.g. 250–600 ms). Tap while red: expect "Too soon!".

90-minute timing: 0–10 plan/sketch — sketch the red → green flow; 10–20 demo — Rica plays one round; 20–65 build — Clock + random wait + time blocks; 65–80 test & fix — play 5 rounds, check Best only improves; 80–90 share — fastest reaction wins, screenshot the best time. Test checklist: Green appears after a random 1–3 s wait; tapping green shows a time in ms; tapping red shows "Too soon!"; Best never gets worse. Common bug: time shows 0 ms or a huge number — fix: check startTime is set inside Clock1.Timer (when it turns green), not inside ButtonStart.Click. Success check: Gin can play a full round and explain how the Clock measures his reaction. Homework: Play 10 rounds at home and write down his best time.

Session 10Catch game — moving image, score, livesWed 20 Jan 2027
Wed 20 Jan 2027 | Phase 2 — Games & Interaction

Date: Wed 20 Jan 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a catch game where a resistor image moves around a canvas, tapping it scores a point, and missing it costs a life. Components: Canvas1, Width Fill parent, Height 300 pixels; ImageSprite1 (on Canvas1), Picture upload a resistor image (or a drawn circle), Width 60, Height 60; LabelScore, Text "Score: 0", FontSize 22; LabelLives, Text "Lives: 3", FontSize 22; ButtonStart, Text "Start game", FontSize 20, BackgroundColor Green; Clock1, TimerEnabled false, TimerInterval 800. Step-by-step build:

1) Designer setup: New project GinCatchGame. Add LabelScore, LabelLives, Canvas1 with ImageSprite1 inside it (set its X/Y to 100, 100), ButtonStart, Clock1. Upload a small resistor picture for ImageSprite1, or leave the default and set its shape via a coloured image.

2) Blocks setup: Create initialize global score to 0, initialize global lives to 3, initialize global playing to false. Snap when ButtonStart.Click → set global score to 0 → set global lives to 3 → set global playing to true → update both labels → set Clock1.TimerEnabled to true. Snap when Clock1.Timer → set ImageSprite1.X to random integer from 0 to (Canvas1.Width - 60) → set ImageSprite1.Y to random integer from 0 to (Canvas1.Height - 60). Snap when ImageSprite1.Touched → if get global playing then set global score to get global score + 1 → update LabelScore → move the sprite to a new random X/Y at once. Snap when Canvas1.Touched → if get global playing then set global lives to get global lives - 1 → update LabelLives → if get global lives = 0 then set global playing to false → set Clock1.TimerEnabled to false → set LabelScore.Text to join "Game over! Score: " + get global score.

3) Test: Companion — Start, tap the sprite 5 times (score rises), tap empty canvas 3 times (lives fall to 0, game over). Note: a sprite tap also triggers Canvas touched in some versions — if lives fall when catching, add a short "just caught" flag; keep it simple first and test.

90-minute timing: 0–10 plan/sketch — draw the canvas, sprite and lives; 10–20 demo — Rica plays one round; 20–65 build — Canvas + sprite + Clock blocks; 65–80 test & fix — play 3 full games; 80–90 share — highest score wins. Screenshot. Test checklist: Sprite jumps to a new random spot every 0.8 s; tapping it adds 1; tapping empty canvas loses a life; 0 lives ends the game. Common bug: sprite never moves — fix: check Clock1 TimerEnabled is set true in Start, and the Timer block sets X and Y (not just one of them). Success check: Gin can play a full game from Start to Game Over with correct score and lives. Homework: Make the game harder: change Clock1 TimerInterval to 600 and test it.

Session 11Memory game — flip cards, match pairsWed 27 Jan 2027
Wed 27 Jan 2027 | Phase 2 — Games & Interaction

Date: Wed 27 Jan 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a 4-pair memory game where tapping two cards flips them, matching pairs stay face-up, and wrong pairs flip back. Components: 8 Buttons in a 4×2 grid (Button1–Button8), Text "?", FontSize 28, Width 70, Height 70; LabelStatus, Text "Find the pairs!", FontSize 20; LabelPairs, Text "Pairs found: 0 / 4", FontSize 20; ButtonRestart, Text "Restart", FontSize 18; Clock1, TimerEnabled false, TimerInterval 800. Step-by-step build:

1) Designer setup: New project GinMemoryGame. Use two HorizontalArrangements (4 buttons each) for the grid. Set all 8 buttons' Text to "?".

2) Blocks setup: Create initialize global cards to make a list ["Ω", "Ω", "V", "V", "I", "I", "R", "R"] (electronics symbols, 4 pairs), initialize global firstPick to 0, initialize global secondPick to 0, initialize global pairsFound to 0, initialize global lock to false. Make a procedure shuffleCards: set global cards to a shuffled copy (use a loop: for each position, swap with a random position — or pre-shuffle the list order by hand in the blocks and note it as a simpler version). Make a procedure flipCard (button, index): if not get global lock and get button.Text = "?" then set button.Text to select list item (get global cards, index) → if get global firstPick = 0 then set global firstPick to index else set global secondPick to index → set global lock to true → set Clock1.TimerEnabled to true. Snap each Button.Click → call flipCard (that button, its number 1–8). Snap when Clock1.Timer → set Clock1.TimerEnabled to false → if select list item (cards, firstPick) = select list item (cards, secondPick) then set global pairsFound to get global pairsFound + 1 → update LabelPairs → set LabelStatus.Text to "Match!" → if get global pairsFound = 4 then set LabelStatus.Text to "You win! All 4 pairs!" → else (no match) set both picked buttons' Text back to "?" → set LabelStatus.Text to "Try again!" → reset firstPick and secondPick to 0, set global lock to false. Snap when ButtonRestart.Click → reset all buttons to "?", pairsFound to 0, firstPick/secondPick to 0, reshuffle.

3) Test: Companion — tap two matching cards (they stay up, Pairs 1/4); tap two different cards (they flip back after 0.8 s); find all 4 pairs for the win message.

90-minute timing: 0–10 plan/sketch — draw the 8-card grid, list the 4 pairs; 10–20 demo — Rica plays with 2 pairs; 20–65 build — grid + flip/match blocks; 65–80 test & fix — play 2 full games; 80–90 share — who finishes in fewest taps? Screenshot. Test checklist: Matching pair stays face-up; wrong pair flips back; Pairs counter reaches 4/4 and shows "You win!"; Restart resets everything. Common bug: cards flip back instantly or never flip back — fix: check Clock1 TimerInterval is 800 and TimerEnabled is set true only after the second pick, and that the Timer block resets lock to false. Success check: Gin can complete a full game and explain how the app remembers the first pick. Homework: Change the pairs to resistor colour names (e.g. "Brown"/"Brown") and test it.

Session 12Maze game — canvas, ball, tilt / buttons to moveWed 3 Feb 2027
Wed 3 Feb 2027 | Phase 2 — Games & Interaction

Date: Wed 3 Feb 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a maze game where a ball moves around a canvas with direction buttons (and tilt as a stretch), reaching the goal wins. Components: Canvas1, Width Fill parent, Height 350 pixels; Ball1 (Ball component on Canvas1), Radius 15, X 30, Y 30, Speed 0; ImageSpriteGoal (on Canvas1), Picture a star/flag image, X 250, Y 280, Width 50, Height 50; ButtonUp, Text "▲", FontSize 24; ButtonDown, Text "▼"; ButtonLeft, Text "◀"; ButtonRight, Text "▶"; LabelStatus, Text "Reach the star!", FontSize 20; ButtonReset, Text "Reset", FontSize 18. Step-by-step build:

1) Designer setup: New project GinMazeGame. Add Canvas1 with Ball1 and ImageSpriteGoal. Draw maze walls on the Canvas using the Canvas DrawLine blocks at start, or place 4–5 thin ImageSprites as wall blocks — simplest: draw walls in the Screen Initialize (see step 2). Add the four direction buttons in a cross layout below the Canvas, plus LabelStatus and ButtonReset.

2) Blocks setup: Snap when Screen1.Initialize → call Canvas1.DrawLine (x1 0, y1 100, x2 200, y2 100) and 3–4 more DrawLine calls to make simple walls, leaving a path to the goal. Snap each direction button: when ButtonUp.Click → set Ball1.Y to get Ball1.Y - 20, Down + 20, Left set Ball1.X to get Ball1.X - 20, Right + 20. Snap when Ball1.CollidedWith → if get other = ImageSpriteGoal then set LabelStatus.Text to "You win! You reached the star!" (Ball CollidedWith gives the other sprite; compare its name). Add a wall check simply: after each move, if Ball1.X < 0 then set Ball1.X to 0, and the same for the other three edges, so the ball stays on the canvas. Snap when ButtonReset.Click → set Ball1.X to 30 → set Ball1.Y to 30 → set LabelStatus.Text to "Reach the star!" → re-draw the walls. Stretch: add AccelerometerSensor1 and move the ball with X/Y tilt instead of buttons.

3) Test: Companion — move the ball with the buttons to the star; the win message appears. Tap Reset; the ball returns to the start.

90-minute timing: 0–10 plan/sketch — draw the maze on paper with walls and a path; 10–20 demo — Rica moves a ball to a goal; 20–65 build — Canvas + ball + buttons; 65–80 test & fix — walk the whole path, check the ball cannot leave the canvas; 80–90 share — race to the star. Screenshot. Test checklist: All four buttons move the ball 20 px in the right direction; reaching the star shows the win message; Reset returns the ball to the start; ball stays inside the canvas. Common bug: ball moves the wrong way (Up goes down) — fix: remember Y grows downwards in App Inventor, so Up must subtract from Y. Success check: Gin can steer the ball through his maze to the goal using only the buttons. Homework: Add one more wall line and one more goal sprite, and test the new path.

Session 13Quiz game 2 — timed questions, levelsWed 10 Feb 2027
Wed 10 Feb 2027 | Phase 2 — Games & Interaction

Date: Wed 10 Feb 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can upgrade his quiz with a 10-second timer per question and two levels (Easy, then Hard) that unlock after 3 correct answers. Components: LabelLevel, Text "Level 1 — Easy", FontSize 20, FontBold true; LabelTimer, Text "Time: 10", FontSize 22; LabelQuestion, Text "Question 1", FontSize 22; ButtonA–ButtonD, Text "A"–"D", FontSize 18; LabelFeedback, Text "", FontSize 20; LabelScore, Text "Score: 0", FontSize 20; Clock1, TimerEnabled false, TimerInterval 1000. Step-by-step build:

1) Designer setup: New project GinTimedQuiz (copy Session 5 and add LabelLevel, LabelTimer, Clock1).

2) Blocks setup: Create initialize global questionsEasy (5 questions) and initialize global questionsHard (5 harder questions, e.g. "Brown-Black-Red = ?" → "1,000 Ω", "Series total of 100 Ω + 200 Ω = ?" → "300 Ω"), plus matching answersEasy, answersHard, choicesEasy, choicesHard lists, initialize global qIndex to 1, initialize global score to 0, initialize global level to 1, initialize global timeLeft to 10. Make a procedure showQuestion: pick the current level's lists, set LabelQuestion and ButtonA–D, set global timeLeft to 10, set LabelTimer.Text to "Time: 10", set Clock1.TimerEnabled to true. Snap when Clock1.Timer → set global timeLeft to get global timeLeft - 1 → update LabelTimer → if get global timeLeft = 0 then set Clock1.TimerEnabled to false → set LabelFeedback.Text to "Time's up!" → move to next question after a short pause (call nextQuestion). Snap each answer button: stop the Clock (set Clock1.TimerEnabled to false), check the answer as in Session 5, add 1 if correct, then if get global score = 3 and get global level = 1 then set global level to 2 → set LabelLevel.Text to "Level 2 — Hard" → set global qIndex to 1 → call showQuestion, else call nextQuestion (qIndex + 1, or end with final score when the list ends).

3) Test: Companion — answer Q1 correctly within 10 s (score 1); wait 10 s on a question (timer hits 0, "Time's up!", moves on); get 3 correct to unlock Level 2 — Hard.

90-minute timing: 0–10 plan/sketch — write 5 Easy + 5 Hard questions on paper; 10–20 demo — Rica plays one timed question; 20–65 build — timer + level blocks; 65–80 test & fix — play through Level 1 into Level 2; 80–90 share — who reaches Level 2 fastest? Screenshot. Test checklist: Timer counts 10 → 0 and moves on at 0; a correct answer stops the timer and scores 1; 3 correct unlocks Level 2; Level 2 shows the harder questions. Common bug: timer keeps running after an answer — fix: set Clock1.TimerEnabled to false inside every answer button, before checking the answer. Success check: Gin can play from Level 1 into Level 2 with the timer working on every question. Homework: Write 2 more Hard questions and add them to the Hard lists.

Session 14Snake-style game — canvas, direction buttons, growing tailWed 17 Feb 2027
Wed 17 Feb 2027 | Phase 2 — Games & Interaction

Date: Wed 17 Feb 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a snake-style game where a ball moves on its own, direction buttons steer it, eating food grows the tail, and hitting a wall ends the game. Components: Canvas1, Width 320, Height 320; Ball1 (head), Radius 12, X 160, Y 160; ImageSpriteFood (on Canvas1), Picture a small circle/apple image, Width 30, Height 30, X 80, Y 80; LabelScore, Text "Score: 0", FontSize 22; LabelStatus, Text "Press Start", FontSize 20; ButtonUp/Down/Left/Right, Text "▲ ▼ ◀ ▶", FontSize 24; ButtonStart, Text "Start", FontSize 20, BackgroundColor Green; Clock1, TimerEnabled false, TimerInterval 200. Step-by-step build:

1) Designer setup: New project GinSnakeGame. Add Canvas1 with Ball1 and ImageSpriteFood, the score/status labels, four direction buttons and ButtonStart, Clock1.

2) Blocks setup: Create initialize global score to 0, initialize global direction to "right", initialize global tail to make a list [] (list of tail segment positions — simplified: keep a tailLength number and draw the tail as a growing list of X/Y pairs), initialize global playing to false. Snap when ButtonStart.Click → reset score, direction "right", Ball1 X/Y to centre, set global playing to true, set Clock1.TimerEnabled to true. Snap direction buttons: when ButtonUp.Click → set global direction to "up" (and so on; block reversing into itself: if direction is "down", ignore "up"). Snap when Clock1.Timer → move the head: if get global direction = "right" then set Ball1.X to get Ball1.X + 20 (same pattern for left/up/down) → add the old head position to the tail list and remove the oldest if the tail is longer than tailLength → if Ball1.X < 0 or Ball1.X > Canvas1.Width or Ball1.Y < 0 or Ball1.Y > Canvas1.Height then gameOver (set playing false, TimerEnabled false, LabelStatus "Game over — hit the wall!"). Snap when Ball1.CollidedWith → if get other = ImageSpriteFood then set global score to get global score + 1 → update LabelScore → set global tailLength to get global tailLength + 1 → move food to a new random X/Y (random integer from 0 to Canvas1.Width - 30). Make a procedure gameOver: stop the Clock, show "Game over! Score: X".

3) Test: Companion — Start, steer with buttons, eat the food (score 1, tail grows by one), drive into a wall (game over). Keep the tail simple: if drawing every segment is too much, show tail length as a number label "Tail: 3" and grow the head's radius slightly — note the simplification in the build.

90-minute timing: 0–10 plan/sketch — draw the snake, food and walls; 10–20 demo — Rica steers one snake; 20–65 build — Clock movement + food + walls; 65–80 test & fix — play 3 games, check food respawns; 80–90 share — highest score wins. Screenshot. Test checklist: Snake moves on its own every 0.2 s; buttons change direction; eating food adds 1 and moves the food; hitting a wall ends the game. Common bug: snake moves through the wall or the food never respawns — fix: check the wall test uses or (any edge) and the food move is inside the CollidedWith block, not the Timer. Success check: Gin can play a full snake game, eat food, and lose by hitting a wall. Homework: Change Clock1 TimerInterval to 150 (faster) and record his new best score.

Session 15Space shooter — sprite, firing, collisionWed 24 Feb 2027
Wed 24 Feb 2027 | Phase 2 — Games & Interaction

Date: Wed 24 Feb 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a space shooter where a ship moves left/right, fires a bullet, and hitting an enemy sprite scores a point. Components: Canvas1, Width Fill parent, Height 350; ImageSpriteShip (on Canvas1), Picture a ship/rocket image, Width 60, Height 60, X 140, Y 280; ImageSpriteEnemy (on Canvas1), Picture an alien/planet image, Width 50, Height 50, X 140, Y 40; BallBullet (Ball on Canvas1), Radius 8, X -100, Y -100, Speed 0 (hidden off-screen until fired); ButtonLeft, Text "◀", FontSize 24; ButtonRight, Text "▶"; ButtonFire, Text "FIRE!", FontSize 22, BackgroundColor Red; LabelScore, Text "Score: 0", FontSize 22; ClockEnemy, TimerEnabled false, TimerInterval 1000. Step-by-step build:

1) Designer setup: New project GinSpaceShooter. Add Canvas1 with the ship at the bottom, enemy at the top, and BallBullet parked off-screen (X -100). Add the three buttons and LabelScore, ClockEnemy.

2) Blocks setup: Create initialize global score to 0, initialize global enemyDirection to 1. Snap when ButtonLeft.Click → set ImageSpriteShip.X to get ImageSpriteShip.X - 20, Right + 20 (clamp: if X < 0 set to 0; if X > Canvas1.Width - 60 set to Canvas1.Width - 60). Snap when ButtonFire.Click → set BallBullet.X to (get ImageSpriteShip.X + 25) → set BallBullet.Y to get ImageSpriteShip.Y → set BallBullet.Speed to 20 → set BallBullet.Heading to 90 (up in App Inventor is 90°). Snap when BallBullet.CollidedWith → if get other = ImageSpriteEnemy then set global score to get global score + 1 → update LabelScore → move the enemy to a new random X at the top (set ImageSpriteEnemy.X to random integer from 0 to Canvas1.Width - 50, Y to 40) → park the bullet off-screen again (X -100, Speed 0). Snap when ClockEnemy.Timer → set ImageSpriteEnemy.X to get ImageSpriteEnemy.X + (20 × get global enemyDirection) → if ImageSpriteEnemy.X > Canvas1.Width - 50 or ImageSpriteEnemy.X < 0 then set global enemyDirection to get global enemyDirection × -1. Add a start: when Screen1.Initialize → set ClockEnemy.TimerEnabled to true.

3) Test: Companion — move the ship, tap FIRE, hit the enemy (score 1, enemy jumps to a new spot). Miss: bullet flies off the top; fire again.

90-minute timing: 0–10 plan/sketch — draw ship, enemy, bullet path; 10–20 demo — Rica fires one shot; 20–65 build — ship + bullet + enemy blocks; 65–80 test & fix — hit the enemy 5 times; 80–90 share — first to 5 hits wins. Screenshot. Test checklist: Ship moves left/right and stays on the canvas; FIRE launches a bullet upward; a hit adds 1 and moves the enemy; the enemy drifts side to side. Common bug: bullet flies sideways or never appears — fix: check Heading is 90 (up) and the bullet's X/Y are set from the ship's position before Speed is set. Success check: Gin can hit the enemy 3 times in a row and explain what CollidedWith does. Homework: Add a second enemy sprite that moves the opposite way.

Session 16Pong / breakout — paddle, ball physics with blocksWed 3 Mar 2027
Wed 3 Mar 2027 | Phase 2 — Games & Interaction

Date: Wed 3 Mar 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a breakout game where a paddle bounces a ball, the ball breaks bricks, and missing the ball loses a life. Components: Canvas1, Width Fill parent, Height 350; ImageSpritePaddle (on Canvas1), Picture a rectangle image, Width 80, Height 15, X 120, Y 310; Ball1 (on Canvas1), Radius 12, X 160, Y 150, Speed 10, Heading 45; 6 ImageSpriteBricks (Brick1–Brick6, on Canvas1), Width 50, Height 20, arranged in a row near the top; LabelScore, Text "Score: 0", FontSize 22; LabelLives, Text "Lives: 3", FontSize 22; ButtonLeft, Text "◀"; ButtonRight, Text "▶"; Clock1, TimerEnabled false, TimerInterval 50. Step-by-step build:

1) Designer setup: New project GinBreakout. Add Canvas1 with the paddle at the bottom, Ball1 in the middle, and 6 bricks in a row at Y = 30 (X = 10, 70, 130, 190, 250, 310 — adjust to canvas width). Add LabelScore, LabelLives, the two buttons, Clock1.

2) Blocks setup: Create initialize global score to 0, initialize global lives to 3, initialize global bricksLeft to 6. Snap when ButtonLeft.Click → set ImageSpritePaddle.X to get ImageSpritePaddle.X - 25, Right + 25 (clamp to the canvas edges). Snap when Screen1.Initialize → set Ball1.Speed to 10 → set Ball1.Heading to 45 → set Clock1.TimerEnabled to true (the Ball moves itself once Speed is set; the Clock is used for the lives check). Snap when Ball1.EdgeReached → if get edge = "Bottom" then lose a life (see below) → else the ball bounces automatically (EdgeReached fires and the Ball bounces by default — keep it). Snap when Ball1.CollidedWith → if get other = ImageSpritePaddle then set Ball1.Heading to (180 - get Ball1.Heading) (bounce up) → else if the other is a brick: set that brick.Visible to false → set global score to get global score + 1 → update LabelScore → set global bricksLeft to get global bricksLeft - 1 → if get global bricksLeft = 0 then set LabelStatus.Text to "You win! All bricks broken!" → stop the ball (Speed 0). Make a procedure loseLife: set global lives to get global lives - 1 → update LabelLives → if get global lives = 0 then set Ball1.Speed to 0 → set LabelScore.Text to "Game over!" → else reset Ball1 X/Y to the middle and Heading to 45. Simplify the brick check: use one CollidedWith block with if/else if checks for Brick1…Brick6 — long but explicit; if time is short, use 3 bricks instead of 6.

3) Test: Companion — move the paddle, bounce the ball, break a brick (score 1, brick disappears); let the ball pass the paddle (lose a life); break all bricks for the win.

90-minute timing: 0–10 plan/sketch — draw paddle, ball, bricks; 10–20 demo — Rica bounces the ball once; 20–65 build — paddle + ball + brick blocks; 65–80 test & fix — play 3 games; 80–90 share — who breaks the most bricks? Screenshot. Test checklist: Paddle moves and stays on the canvas; ball bounces off walls and paddle; hitting a brick removes it and adds 1; missing the ball loses a life; 0 lives ends the game. Common bug: ball passes through the paddle — fix: check the CollidedWith block compares other with ImageSpritePaddle and that the paddle is an ImageSprite on the same Canvas, not a Button. Success check: Gin can break at least 3 bricks in one game and explain how the ball bounces. Homework: Add a second row of 6 bricks and test it.

Session 17Dice & random — random numbers, dice roller appWed 10 Mar 2027
Wed 10 Mar 2027 | Phase 2 — Games & Interaction

Date: Wed 10 Mar 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a dice roller that shows a random 1–6 on each tap, keeps a history list, and can roll two dice and add them. Components: LabelDice, Text "🎲 ?", FontSize 60; LabelDice2, Text "🎲 ?", FontSize 60; ButtonRoll, Text "Roll the dice!", FontSize 22, BackgroundColor Blue; ButtonRoll2, Text "Roll two dice", FontSize 18; LabelTotal, Text "Total: —", FontSize 22; LabelHistory, Text "History: ", FontSize 18; ButtonClear, Text "Clear history", FontSize 18. Step-by-step build:

1) Designer setup: New project GinDiceRoller. Add LabelDice and LabelDice2 side by side in a HorizontalArrangement, then ButtonRoll, ButtonRoll2, LabelTotal, LabelHistory, ButtonClear.

2) Blocks setup: Create initialize global history to make a list [], initialize global die1 to 0, initialize global die2 to 0. Snap when ButtonRoll.Click → set global die1 to random integer from 1 to 6 → set LabelDice.Text to get global die1 (use a dice-face text or the number; if using emoji dice, use a list lookup: select list item (make a list ["⚀","⚁","⚂","⚃","⚄","⚅"], get global die1)) → add item get global die1 to list get global history → set LabelHistory.Text to join "History: " + get global history. Snap when ButtonRoll2.Click → roll die1 and die2 the same way, set both labels, set LabelTotal.Text to join "Total: " + (get global die1 + get global die2) → add the total to history. Snap when ButtonClear.Click → set global history to make a list [] → set LabelHistory.Text to "History: ".

3) Test: Companion — tap Roll 10 times; each result is 1–6 and history grows. Tap Roll two dice: Total is the sum of the two dice shown (e.g. 3 + 4 = 7).

90-minute timing: 0–10 plan/sketch — draw two dice, list what "random" means; 10–20 demo — Rica rolls 5 times; 20–65 build — random + history blocks; 65–80 test & fix — roll 20 times, check no 0 or 7 appears; 80–90 share — highest total in 3 rolls of two dice wins. Screenshot. Test checklist: Single roll always shows 1–6; two-dice total equals the two dice added; history lists every roll; Clear empties history. Common bug: total is wrong (e.g. 3 + 4 shows 34) — fix: the dice were joined as text; use the math + block on the two number variables. Success check: Gin can explain what random integer from 1 to 6 does and his history matches his rolls. Homework: Roll two dice 10 times at home and write down how many times the total was 7.

Session 18Rock-paper-scissors — random opponent, scoreboardWed 17 Mar 2027
Wed 17 Mar 2027 | Phase 2 — Games & Interaction

Date: Wed 17 Mar 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build rock-paper-scissors where the phone picks randomly, the app decides the winner, and a scoreboard tracks wins, losses and draws. Components: LabelTitle, Text "Rock, Paper, Scissors!", FontSize 24, FontBold true; ButtonRock, Text "✊ Rock", FontSize 20; ButtonPaper, Text "✋ Paper", FontSize 20; ButtonScissors, Text "✌️ Scissors", FontSize 20; LabelOpponent, Text "Opponent: ?", FontSize 22; LabelResult, Text "Pick one!", FontSize 22, FontBold true; LabelScore, Text "Wins: 0 Losses: 0 Draws: 0", FontSize 20; ButtonReset, Text "Reset score", FontSize 18. Step-by-step build:

1) Designer setup: New project GinRockPaperScissors. Add the title, three choice buttons in a HorizontalArrangement, LabelOpponent, LabelResult, LabelScore, ButtonReset.

2) Blocks setup: Create initialize global wins to 0, initialize global losses to 0, initialize global draws to 0, initialize global choices to make a list ["Rock", "Paper", "Scissors"]. Make a procedure play (myChoice): set global opponent to select list item (get global choices, random integer from 1 to 3) → set LabelOpponent.Text to join "Opponent: " + get global opponent → if get myChoice = get global opponent then set global draws to get global draws + 1 → set LabelResult.Text to "Draw!" → else if (myChoice = "Rock" and opponent = "Scissors") or (myChoice = "Paper" and opponent = "Rock") or (myChoice = "Scissors" and opponent = "Paper") then set global wins to get global wins + 1 → set LabelResult.Text to "You win!" → else set global losses to get global losses + 1 → set LabelResult.Text to "You lose!" → update LabelScore with join "Wins: " + wins + " Losses: " + losses + " Draws: " + draws. Snap when ButtonRock.Click → call play "Rock", Paper → call play "Paper", Scissors → call play "Scissors". Snap when ButtonReset.Click → set wins, losses, draws to 0 and update LabelScore.

3) Test: Companion — play 10 rounds; wins + losses + draws must equal 10; Rock vs Scissors is a win; same choice is a draw.

90-minute timing: 0–10 plan/sketch — write the win rules (Rock beats Scissors, etc.); 10–20 demo — Rica plays 3 rounds; 20–65 build — random opponent + winner blocks; 65–80 test & fix — play 10 rounds, check the scoreboard adds up; 80–90 share — first to 5 wins. Screenshot. Test checklist: Opponent's choice changes each round; the winner is decided correctly for all 9 combinations; scoreboard totals match rounds played; Reset clears all three counts. Common bug: Paper vs Rock says "You lose!" — fix: check the win or chain: Paper beats Rock, so that pair must be in the win branch, not the lose branch. Success check: Gin can play 10 rounds with a correct scoreboard and state the three win rules. Homework: Play 20 rounds and write down wins, losses and draws.

Session 19Two-player tap battle — same screen, two buttonsWed 24 Mar 2027
Wed 24 Mar 2027 | Phase 2 — Games & Interaction

Date: Wed 24 Mar 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a two-player tap battle on one phone: two big buttons, a 10-second countdown, and a winner announcement. Components: LabelTitle, Text "Tap Battle!", FontSize 24, FontBold true; LabelTimer, Text "Time: 10", FontSize 24; ButtonP1, Text "PLAYER 1\nTAP!", FontSize 24, BackgroundColor Blue, Height 200 pixels; ButtonP2, Text "PLAYER 2\nTAP!", FontSize 24, BackgroundColor Red, Height 200 pixels; LabelScore1, Text "P1: 0", FontSize 22; LabelScore2, Text "P2: 0", FontSize 22; LabelWinner, Text "", FontSize 26, FontBold true; ButtonStart, Text "Start battle", FontSize 20, BackgroundColor Green; Clock1, TimerEnabled false, TimerInterval 1000. Step-by-step build:

1) Designer setup: New project GinTapBattle. Add LabelTitle, LabelTimer, ButtonP1 and ButtonP2 side by side in a HorizontalArrangement (each Width 50%), LabelScore1 and LabelScore2, LabelWinner, ButtonStart, Clock1. Set ButtonP1 and ButtonP2 Enabled false at first.

2) Blocks setup: Create initialize global score1 to 0, initialize global score2 to 0, initialize global timeLeft to 10, initialize global playing to false. Snap when ButtonStart.Click → reset both scores, timeLeft to 10, set global playing to true, enable both tap buttons, clear LabelWinner, set Clock1.TimerEnabled to true. Snap when ButtonP1.Click → if get global playing then set global score1 to get global score1 + 1 → update LabelScore1. Same for ButtonP2 with score2. Snap when Clock1.Timer → set global timeLeft to get global timeLeft - 1 → update LabelTimer → if get global timeLeft = 0 then set Clock1.TimerEnabled to false → set global playing to false → disable both tap buttons → if get global score1 > get global score2 then set LabelWinner.Text to "Player 1 wins!" → else if score2 > score1 then "Player 2 wins!" → else "It's a draw!".

3) Test: Companion — Start, tap both buttons with two hands for 10 seconds; when the timer hits 0 the buttons stop and the winner is announced correctly.

90-minute timing: 0–10 plan/sketch — draw the split screen, two players; 10–20 demo — Rica vs Gin, one 10-second round; 20–65 build — two-button + countdown blocks; 65–80 test & fix — play 3 battles, check the winner each time; 80–90 share — Gin vs Ray, Gin vs Run. Screenshot the winner screen. Test checklist: Both buttons count only during the 10 seconds; timer counts 10 → 0; buttons stop at 0; winner matches the higher score; a tie says "It's a draw!". Common bug: taps after time still count — fix: check both tap blocks start with if get global playing and that playing is set false when timeLeft hits 0. Success check: Gin can run a full 10-second battle with a friend and the correct winner is announced. Homework: Change the battle length to 15 seconds and test it.

Session 20Soundboard game — sounds, images, combosWed 31 Mar 2027
Wed 31 Mar 2027 | Phase 2 — Games & Interaction

Date: Wed 31 Mar 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a soundboard with 6 sound buttons, each playing a different sound and showing its picture, plus a combo that plays two sounds in order. Components: 6 Buttons (Button1–Button6) with images: e.g. ButtonBuzzer "Buzzer", ButtonBeep "Beep", ButtonBell "Bell", ButtonClick "Click", ButtonAlarm "Alarm", ButtonPop "Pop", FontSize 18; LabelNow, Text "Tap a sound!", FontSize 20; ButtonCombo, Text "Play combo!", FontSize 20, BackgroundColor Purple; Sound1 (non-visible); Player1 (non-visible, for longer sounds if needed). Step-by-step build:

1) Designer setup: New project GinSoundboard. Add the 6 buttons in a 3×2 grid (two HorizontalArrangements), LabelNow, ButtonCombo, Sound1. Upload 6 short sound files (use MIT App Inventor's built-in sounds or free short clips — e.g. buzzer, beep, bell) and set Sound1 Source to the first one; the other sounds are set in Blocks by changing Source before playing.

2) Blocks setup: Create initialize global sounds to make a list ["buzzer.mp3", "beep.mp3", "bell.mp3", "click.mp3", "alarm.mp3", "pop.mp3"] (use the exact uploaded file names). Make a procedure playSound (soundFile, name): set Sound1.Source to get soundFile → call Sound1.Play → set LabelNow.Text to join "Now playing: " + get name. Snap each button: when Button1.Click → call playSound "buzzer.mp3" "Buzzer" (and so on for the other five). Snap when ButtonCombo.Click → call playSound "beep.mp3" "Beep" → call Sound1.Play again after a short delay is hard without a Clock, so use Clock1 (TimerInterval 500, TimerEnabled false): set a global comboStep to 1, enable Clock1; when Clock1.Timer → if comboStep = 1 play "bell.mp3", set comboStep to 2; else if comboStep = 2 play "pop.mp3", disable Clock1, set LabelNow to "Combo done!". If the Clock combo is too fiddly, simplify: the combo button plays three sounds by setting Source and calling Play three times in a row — note that they may overlap, and the Clock version is the tidy fix.

3) Test: Companion — tap each of the 6 buttons; each plays its own sound and LabelNow names it. Tap Combo: two or three sounds play in order.

90-minute timing: 0–10 plan/sketch — list 6 sounds and what each button does; 10–20 demo — Rica plays a mini soundboard; 20–65 build — Sound component + play blocks; 65–80 test & fix — tap every button, check each sound is different; 80–90 share — Gin performs a "sound story" with the board. Screenshot. Test checklist: All 6 buttons play a sound; LabelNow names the sound played; Combo plays more than one sound in order; no button is silent. Common bug: every button plays the same sound — fix: check each button's playSound call passes its own file name, and that Sound1.Source is set before Play is called. Success check: Gin can play all 6 sounds and a combo, and explain what the Sound component does. Homework: Find one new sound file and add a 7th button for it.

Session 21Card game — draw a card, higher / lowerWed 7 Apr 2027
Wed 7 Apr 2027 | Phase 2 — Games & Interaction

Date: Wed 7 Apr 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a higher/lower card game: draw a card, guess whether the next card is higher or lower, and keep score over 10 rounds. Components: LabelCard, Text "🂠 ?", FontSize 60; LabelNext, Text "Next card: ?", FontSize 24; ButtonHigher, Text "Higher ▲", FontSize 20, BackgroundColor Green; ButtonLower, Text "Lower ▼", FontSize 20, BackgroundColor Blue; LabelScore, Text "Score: 0 / 10", FontSize 20; LabelRound, Text "Round: 1 / 10", FontSize 20; LabelResult, Text "Draw a card to start!", FontSize 20; ButtonStart, Text "Start game", FontSize 20. Step-by-step build:

1) Designer setup: New project GinHigherLower. Add LabelCard, LabelNext, ButtonHigher and ButtonLower side by side, LabelScore, LabelRound, LabelResult, ButtonStart.

2) Blocks setup: Create initialize global currentCard to 0, initialize global score to 0, initialize global round to 1, initialize global playing to false. Make a procedure drawCard: set global currentCard to random integer from 1 to 13 → set LabelCard.Text to join "Card: " + get global currentCard (1 = Ace low, 11 = Jack, 12 = Queen, 13 = King — say this in the label: use a list ["A","2","3","4","5","6","7","8","9","10","J","Q","K"] and select list item for the display). Snap when ButtonStart.Click → reset score and round, set global playing to true, call drawCard, set LabelResult.Text to "Higher or lower?". Make a procedure guess (higher?): set global nextCard to random integer from 1 to 13 → set LabelNext.Text to join "Next card: " + nextCard name → if get higher? = true and get global nextCard > get global currentCard then correct → else if higher? is false and nextCard < currentCard then correct → else if nextCard = currentCard then set LabelResult.Text to "Same card — no point!" → else set LabelResult.Text to "Wrong!" → if correct, score + 1 and LabelResult "Correct!" → update LabelScore → set global currentCard to get global nextCard → set global round to get global round + 1 → if get global round > 10 then set LabelResult.Text to join "Game over! Score: " + get global score + " / 10" → set global playing to false else update LabelRound. Snap when ButtonHigher.Click → if get global playing then call guess true, Lower → call guess false.

3) Test: Companion — Start, guess Higher 10 times; score only rises when the next card really is higher; after round 10 the game ends with a final score.

90-minute timing: 0–10 plan/sketch — draw two cards, write the higher/lower rule; 10–20 demo — Rica plays 3 rounds; 20–65 build — random card + guess blocks; 65–80 test & fix — play a full 10-round game; 80–90 share — who scores highest in 10 rounds? Screenshot. Test checklist: Cards show 1–13 (A–K); Higher is correct only when the next card is higher; a tie gives no point; after 10 rounds the final score shows and buttons stop. Common bug: score rises even on a wrong guess — fix: check the guess procedure compares nextCard with currentCard (not with itself) and that currentCard is updated to nextCard after each round. Success check: Gin can play a full 10-round game with correct scoring and explain the tie rule. Homework: Play 10 rounds and write down the final score.

Session 22Word game — scrambled electronics words, hintsWed 14 Apr 2027
Wed 14 Apr 2027 | Phase 2 — Games & Interaction

Date: Wed 14 Apr 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can build a word game that shows a scrambled electronics word, gives a hint, checks the typed answer, and tracks score. Components: LabelScrambled, Text "R O T S I S E R", FontSize 28, FontBold true; LabelHint, Text "Hint: It limits current.", FontSize 18; TextBoxAnswer, Hint "Type the word here"; ButtonCheck, Text "Check!", FontSize 20, BackgroundColor Green; ButtonHint, Text "Another hint", FontSize 18; ButtonNext, Text "Next word", FontSize 18; LabelFeedback, Text "", FontSize 20; LabelScore, Text "Score: 0 / 5", FontSize 20. Step-by-step build:

1) Designer setup: New project GinWordGame. Add LabelScrambled, LabelHint, TextBoxAnswer, ButtonCheck, ButtonHint, ButtonNext, LabelFeedback, LabelScore.

2) Blocks setup: Create initialize global words to make a list ["RESISTOR", "VOLTAGE", "CURRENT", "CIRCUIT", "BATTERY"], initialize global scrambled to make a list ["ROTSISER", "EGLATOV", "TNERRUC", "TICURCI", "YRETTAB"], initialize global hints to make a list ["It limits current.", "Measured in volts, V = I × R.", "Measured in amps, flows in a circuit.", "A loop that electricity flows around.", "It stores energy and gives power."], initialize global hints2 to make a list ["Brown-Black-Red is one of these.", "The V in Ohm's Law.", "The I in Ohm's Law.", "It has a resistor, a battery and wires.", "You put it in a remote control."], initialize global wordIndex to 1, initialize global score to 0. Make a procedure showWord: set LabelScrambled to the scrambled word at wordIndex, LabelHint to the first hint, clear TextBoxAnswer and LabelFeedback. Snap when ButtonCheck.Click → if upcase (get TextBoxAnswer.Text) = select list item (get global words, get global wordIndex) then set global score to get global score + 1 → set LabelFeedback.Text to "Correct!" → update LabelScore → else set LabelFeedback.Text to "Try again!". (App Inventor has an upcase text block — use it so "resistor" counts as correct.) Snap when ButtonHint.Click → set LabelHint.Text to select list item (get global hints2, get global wordIndex). Snap when ButtonNext.Click → set global wordIndex to get global wordIndex + 1 → if get global wordIndex > 5 then set LabelScrambled.Text to join "Done! Score: " + get global score + " / 5" → else call showWord. Call showWord in Screen1.Initialize.

3) Test: Companion — unscramble "ROTSISER" → type RESISTOR, tap Check, expect "Correct!" and Score 1/5; tap Another hint on a hard word; finish all 5 for the final score.

90-minute timing: 0–10 plan/sketch — write 5 words, scramble each on paper; 10–20 demo — Rica unscrambles one word; 20–65 build — word lists + check blocks; 65–80 test & fix — play all 5 words; 80–90 share — Ray and Run try one word each. Screenshot. Test checklist: All 5 scrambled words appear in order; RESISTOR is accepted (any capitalisation); a wrong word says "Try again!"; Another hint shows the second hint; finishing shows the final score. Common bug: a correct answer in lower-case counts as wrong — fix: wrap TextBoxAnswer.Text in the upcase block before comparing. Success check: Gin can finish all 5 words with correct scoring and explain why upcase is needed. Homework: Add a 6th word of his own (scrambled + 2 hints) to the lists.

Session 23Game polish — fix bugs, add levels, difficultyWed 21 Apr 2027
Wed 21 Apr 2027 | Phase 2 — Games & Interaction

Date: Wed 21 Apr 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can pick his weakest game, list its bugs, fix them, and add one difficulty feature (faster timer, harder level, or extra lives rule). Components: Depends on the game Gin picks — reuse that project's components. Add: LabelBugs, Text "Bugs to fix:", FontSize 20; ButtonDifficulty, Text e.g. "Hard mode", FontSize 18 (new); LabelDifficulty, Text "Mode: Normal", FontSize 18. Example for the Snake game: Clock1 TimerInterval 200 (Normal) vs 120 (Hard); for the Quiz: timeLeft 10 (Normal) vs 6 (Hard). Step-by-step build:

1) Designer setup: Open the chosen game's project (copy it first: Projects → Save project as GinSnakeGamePolished). Add the ButtonDifficulty and LabelDifficulty components. Write the bug list on paper before touching any blocks: e.g. "1) Food sometimes appears under the score label. 2) Snake can reverse into itself. 3) No way to restart after game over."

2) Blocks setup: Fix each bug in turn, testing after each one — e.g. for the food bug: change the food's random X/Y range to stay inside the canvas and below the labels; for the reverse bug: in each direction button add if get global direction ≠ opposite then set global direction to …; for the restart bug: add when ButtonStart.Click to reset everything (already there — check it resets tailLength and score). Add difficulty: when ButtonDifficulty.Click → if get global mode = "Normal" then set global mode to "Hard" → set Clock1.TimerInterval to 120 → set LabelDifficulty.Text to "Mode: Hard" → else set back to Normal / 200. Test both modes.

3) Test: Companion — play the polished game in Normal, then in Hard; confirm every bug on the list is gone and Hard really is harder.

90-minute timing: 0–10 plan/sketch — list bugs + pick one difficulty feature; 10–20 demo — Rica shows a before/after fix; 20–65 build — fix bugs one by one, then add difficulty; 65–80 test & fix — play 3 games in each mode; 80–90 share — Gin demos the polished game and names the bugs he fixed. Screenshot. Test checklist: Every bug on the paper list is fixed and can be shown; Normal and Hard feel different; the game still works end-to-end (start → play → game over → restart). Common bug: fixing one thing breaks another (e.g. Hard mode never switches back) — fix: check the difficulty button's if/else sets both the mode variable and the TimerInterval in both branches. Success check: Gin can show a before/after for at least two bugs and explain his difficulty feature. Homework: Write a one-line description of the polished game for the showcase next week.

Session 24Games showcase — playtest all games, pick best to keepWed 28 Apr 2027
Wed 28 Apr 2027 | Phase 2 — Games & Interaction

Date: Wed 28 Apr 2027 | Phase: Phase 2 — Games & Interaction Learning objective: Gin can playtest all his Phase 2 games, score each one, and pick his best two to keep and show in his portfolio. Components: No new app — reuse the games from Sessions 9–23. On paper (or a new Screen in a portfolio project): LabelTitle "My Games — Showcase", FontSize 24; a checklist table on paper with columns: Game | Fun 1–5 | Works? | Keep?; ButtonStart for each game is in its own project. Step-by-step build:

1) Designer setup: No new Designer work. Open each game project in turn on the Companion. Make the paper scorecard first: list all games (Reaction, Catch, Memory, Maze, Timed Quiz, Snake, Space Shooter, Breakout, Dice, Rock-Paper-Scissors, Tap Battle, Soundboard, Higher/Lower, Word Game, Polished Game).

2) Blocks setup: No new blocks, except fixing any bug found during playtesting — e.g. if a game crashes on empty input, add the same guard used in Session 8 (if TextBox.Text = "" then show a reminder). Note each fix on the scorecard. If a game is missing a Restart/Start button, add one now using the pattern from Session 10 (when ButtonStart.Click resets score/lives and enables the Clock).

3) Test: Companion — play each game for 3 minutes: does it start, play, end, and restart? Score Fun 1–5 and Works Yes/No. Pick the best two (highest Fun + Works = Yes). Export both as .aia files (Projects → Export selected project) so they are backed up.

90-minute timing: 0–10 plan/sketch — make the scorecard; 10–20 demo — Rica playtests one game and scores it; 20–65 build — playtest every game, fix small bugs; 65–80 test & fix — re-test the fixed games; 80–90 share — Gin presents his best two games to Ray, Run and Rica, 2 minutes each. Screenshot the scorecard. Test checklist: Every game opens and plays; every game has a working start/restart; the two kept games have no known bugs; both .aia files are exported. Common bug: a game that worked last month now fails — fix: check the Companion is up to date and re-open the project; most "breaks" are a renamed component or a disconnected Companion, not a logic bug. Success check: Gin can name his best two games, say why, and show both working. Homework: Write two sentences about each kept game: what it is and what he is proud of.

Session 25Lists basics — make a list app, add / remove itemsWed 5 May 2027
Wed 5 May 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 5 May 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build a list app that adds typed items to a ListView, removes the selected item, and clears the whole list. Components: LabelTitle, Text "My List", FontSize 24, FontBold true; TextBoxItem, Hint "Type an item, e.g. Resistor 1kΩ"; ButtonAdd, Text "Add", FontSize 20, BackgroundColor Green; ListView1, Width Fill parent, Height 250 pixels; ButtonRemove, Text "Remove selected", FontSize 18; ButtonClear, Text "Clear all", FontSize 18, BackgroundColor Red; LabelCount, Text "Items: 0", FontSize 20. Step-by-step build:

1) Designer setup: New project GinListApp. Add the components above in order. Set ListView1 ElementsFromString empty at first.

2) Blocks setup: Create initialize global myList to make a list []. Make a procedure showList: set ListView1.Elements to get global myList → set LabelCount.Text to join "Items: " + length of list get global myList. Snap when ButtonAdd.Click → if get TextBoxItem.Text ≠ "" then add item get TextBoxItem.Text to list get global myList → set TextBoxItem.Text to "" → call showList → else set LabelCount.Text to "Type an item first!". Snap when ListView1.AfterPicking → store the pick: set global selected to get ListView1.Selection. Snap when ButtonRemove.Click → if get global selected ≠ "" then remove list item (list get global myList, index index in list (thing get global selected, list get global myList)) → call showList → set global selected to "" → else set LabelCount.Text to "Tap an item first, then Remove.". Snap when ButtonClear.Click → set global myList to make a list [] → call showList.

3) Test: Companion — add "Resistor 1kΩ", "LED red", "Battery 9V"; ListView shows all three, Count 3. Tap "LED red", tap Remove — it disappears, Count 2. Tap Clear all — list empties.

90-minute timing: 0–10 plan/sketch — draw the list screen, list 3 example items; 10–20 demo — Rica adds/removes items; 20–65 build — ListView + add/remove blocks; 65–80 test & fix — add 5, remove 1, clear all; 80–90 share — Gin builds a list of his real electronics parts. Screenshot. Test checklist: Adding shows the item at once; removing deletes only the tapped item; Clear empties the list; adding an empty box shows the reminder, not a blank item. Common bug: Remove deletes the wrong item or crashes — fix: check the remove block uses index in list to find the tapped item's position, and that selected is set in AfterPicking. Success check: Gin can add, remove and clear items and explain what a ListView shows. Homework: Make a list of 5 things in his electronics kit using the app.

Session 26Component list — electronics parts list, searchWed 12 May 2027
Wed 12 May 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 12 May 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build an electronics parts list with a search box that filters the list as he types, and a detail label for the tapped part. Components: LabelTitle, Text "Electronics Parts", FontSize 24, FontBold true; TextBoxSearch, Hint "Search, e.g. resistor"; ListView1, Width Fill parent, Height 250 pixels; LabelDetail, Text "Tap a part to see details", FontSize 20; ButtonShowAll, Text "Show all", FontSize 18. Step-by-step build:

1) Designer setup: New project GinPartsList. Add the components above.

2) Blocks setup: Create initialize global parts to make a list ["Resistor 1kΩ — limits current, Brown-Black-Red", "Resistor 10kΩ — limits current, Brown-Black-Orange", "LED red — lights up, needs a resistor", "LED green — lights up, needs a resistor", "Battery 9V — powers a circuit", "Switch — turns a circuit on/off", "Breadboard — build circuits without soldering", "Wire red — connects parts", "Capacitor 100µF — stores charge", "Buzzer — makes a sound"], initialize global filtered to make a list []. Make a procedure showList (listToShow): set ListView1.Elements to get listToShow. Snap when Screen1.Initialize → call showList get global parts. Snap when TextBoxSearch.TextChanged → set global filtered to make a list [] → for each item in list get global parts: if contains (text get item, piece get TextBoxSearch.Text) then add item get item to list get global filtered → call showList get global filtered (use the text contains block; note it is case-sensitive — type lower-case or use upcase on both sides). Snap when ListView1.AfterPicking → set LabelDetail.Text to get ListView1.Selection (the full detail string is the item itself). Snap when ButtonShowAll.Click → set TextBoxSearch.Text to "" → call showList get global parts.

3) Test: Companion — type "resistor": only the two resistor rows show. Type "LED": only the two LED rows show. Tap a row: its full detail appears in LabelDetail. Tap Show all: all 10 rows return.

90-minute timing: 0–10 plan/sketch — write the 10 parts and their details on paper; 10–20 demo — Rica searches "LED"; 20–65 build — parts list + search filter blocks; 65–80 test & fix — search 4 different words; 80–90 share — Gin adds one real part from his kit to the list. Screenshot. Test checklist: Searching filters the list live; clearing the search (or Show all) restores all 10; tapping a row shows its detail; no search crashes the app. Common bug: search finds nothing even for "LED" — fix: check the contains block compares the typed text with each item (not the other way round) and watch capital letters — "led" will not match "LED" without upcase. Success check: Gin can search, filter and view details for any part in his list. Homework: Add 3 more real parts from his kit, with a one-line detail each.

Session 27Inventory list — quantities, tick offWed 19 May 2027
Wed 19 May 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 19 May 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build an inventory list that shows each part with a quantity, lets him add or use one, and ticks off items that reach zero. Components: LabelTitle, Text "Parts Inventory", FontSize 24, FontBold true; ListView1, Width Fill parent, Height 250 pixels; LabelDetail, Text "Tap a part", FontSize 20; ButtonAddOne, Text "+1", FontSize 22, BackgroundColor Green; ButtonUseOne, Text "−1 Use one", FontSize 22, BackgroundColor Orange; ButtonAddPart, Text "Add new part", FontSize 18; TextBoxNew, Hint "New part name, e.g. LED blue". Step-by-step build:

1) Designer setup: New project GinInventory. Add the components above.

2) Blocks setup: Create two parallel lists: initialize global names to make a list ["Resistor 1kΩ", "LED red", "Battery 9V", "Wire red"] and initialize global quantities to make a list [10, 5, 2, 20], plus initialize global selectedIndex to 0. Make a procedure showInventory: build a display list with a for each number from 1 to length of list get global names loop — add item join (select list item names, number) + " × " + (select list item quantities, number) to list get global display — then set ListView1.Elements to get global display. Snap when ListView1.AfterPicking → set global selectedIndex to get ListView1.SelectionIndex → set LabelDetail.Text to join (select list item names, selectedIndex) + " — have " + (select list item quantities, selectedIndex). Snap when ButtonAddOne.Click → if get global selectedIndex > 0 then replace list item (list get global quantities, index get global selectedIndex, replacement (select list item quantities, selectedIndex) + 1) → call showInventory + update LabelDetail. Snap when ButtonUseOne.Click → same but - 1, and if the new quantity = 0 then set LabelDetail.Text to join name + " — OUT OF STOCK, tick it off!". Snap when ButtonAddPart.Click → if get TextBoxNew.Text ≠ "" then add item get TextBoxNew.Text to list get global names → add item 1 to list get global quantities → call showInventory.

3) Test: Companion — tap "LED red" (have 5), tap "−1 Use one" twice (have 3); tap "+1" (have 4); use Battery 9V twice (0, "OUT OF STOCK"); add "LED blue" (appears ×1).

90-minute timing: 0–10 plan/sketch — draw the inventory table (part | quantity); 10–20 demo — Rica uses one LED; 20–65 build — parallel lists + quantity blocks; 65–80 test & fix — add/use each part once; 80–90 share — Gin counts his real resistors and enters the true numbers. Screenshot. Test checklist: Tapping a part shows its quantity; +1 and −1 change only that part; reaching 0 shows OUT OF STOCK; adding a new part works with quantity 1. Common bug: +1 changes the wrong part — fix: check selectedIndex comes from SelectionIndex (the tapped row's number) and that names and quantities stay in the same order — never sort one list without the other. Success check: Gin can explain why two parallel lists must stay in the same order, and his inventory quantities are correct. Homework: Count his real LEDs and resistors at home and update the quantities.

Session 28TinyDB basics — save a setting, load it on openWed 26 May 2027
Wed 26 May 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 26 May 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can save a setting with TinyDB and load it automatically when the app opens, so it survives closing the app. Components: TinyDB1 (non-visible); LabelTitle, Text "My Settings", FontSize 24, FontBold true; LabelName, Text "Your name: ", FontSize 20; TextBoxName, Hint "Type your name"; ButtonSaveName, Text "Save name", FontSize 18; LabelSound, Text "Sound: ON", FontSize 20; ButtonSound, Text "Sound ON/OFF", FontSize 18; LabelColour, Text "Favourite colour: ", FontSize 20; ButtonColour, Text "Change colour", FontSize 18 (cycles Blue → Green → Orange). Step-by-step build:

1) Designer setup: New project GinSettings. Add TinyDB1 from Storage (non-visible, below the screen) plus the components above.

2) Blocks setup: Create initialize global soundOn to true, initialize global colourIndex to 1, initialize global colours to make a list ["Blue", "Green", "Orange"]. Snap when Screen1.Initialize → set TextBoxName.Text to call TinyDB1.GetValue tag "name" valueIfTagNotThere "" → set LabelName.Text to join "Your name: " + that value → set global soundOn to call TinyDB1.GetValue tag "sound" valueIfTagNotThere true → update LabelSound ("Sound: ON" / "Sound: OFF") → set global colourIndex to call TinyDB1.GetValue tag "colour" valueIfTagNotThere 1 → set Screen1 BackgroundColor from the colour list. Snap when ButtonSaveName.Click → call TinyDB1.StoreValue tag "name" valueToStore get TextBoxName.Text → set LabelName.Text to join "Your name: " + get TextBoxName.Text. Snap when ButtonSound.Click → set global soundOn to not get global soundOn → call TinyDB1.StoreValue tag "sound" valueToStore get global soundOn → update LabelSound. Snap when ButtonColour.Click → cycle colourIndex 1→2→3→1 → call TinyDB1.StoreValue tag "colour" valueToStore get global colourIndex → set the screen background colour.

3) Test: Companion — type "Gin", Save name, close the app fully (swipe it away), reopen it: the name must still be there. Toggle Sound OFF, close, reopen: still OFF. Change colour, close, reopen: same colour.

90-minute timing: 0–10 plan/sketch — draw the settings screen, list what should be remembered; 10–20 demo — Rica saves a name, closes and reopens; 20–65 build — TinyDB store/load blocks; 65–80 test & fix — close and reopen after every save; 80–90 share — Gin shows his saved name surviving a restart. Screenshot. Test checklist: Name, sound and colour all survive closing and reopening the app; each Save updates at once; first-ever open shows sensible defaults (empty name, Sound ON). Common bug: the setting is gone after reopening — fix: check the tag text matches exactly in StoreValue and GetValue ("name" vs "Name" are different tags) and that loading happens in Screen1.Initialize. Success check: Gin can explain "TinyDB remembers on the phone" and prove it by closing and reopening the app. Homework: Add a 4th setting of his own (e.g. favourite number) with its own tag.

Session 29Save high scores — TinyDB, leaderboardWed 2 Jun 2027
Wed 2 Jun 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 2 Jun 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can save his best scores with TinyDB and show a leaderboard of his top 3 scores across games. Components: TinyDB1 (non-visible); LabelTitle, Text "Leaderboard", FontSize 24, FontBold true; LabelBoard, Text "Top scores:", FontSize 20; ListView1, Width Fill parent, Height 200 pixels; TextBoxGame, Hint "Game name, e.g. Snake"; TextBoxScore, Hint "Score, e.g. 12", NumbersOnly true; ButtonSaveScore, Text "Save score", FontSize 20, BackgroundColor Green; ButtonClear, Text "Clear leaderboard", FontSize 18. Step-by-step build:

1) Designer setup: New project GinLeaderboard. Add TinyDB1 plus the components above.

2) Blocks setup: Create initialize global scores to make a list []. Snap when Screen1.Initialize → set global scores to call TinyDB1.GetValue tag "scores" valueIfTagNotThere make a list [] → set ListView1.Elements to get global scores. Snap when ButtonSaveScore.Click → if get TextBoxScore.Text ≠ "" then add item join (get TextBoxGame.Text + " — " + get TextBoxScore.Text) to list get global scores → call TinyDB1.StoreValue tag "scores" valueToStore get global scores → set ListView1.Elements to get global scores → clear both TextBoxes → else set LabelBoard.Text to "Type a game and a score first!". Stretch: sort the leaderboard — App Inventor has no built-in sort for text, so keep insertion order and note it; a simple improvement is to store "score — game" with the number first (e.g. "12 — Snake") so the list reads biggest-first only if Gin enters them in order. Snap when ButtonClear.Click → set global scores to make a list [] → call TinyDB1.StoreValue tag "scores" valueToStore get global scores → set ListView1.Elements to get global scores.

3) Test: Companion — save "Snake — 12", "Reaction — 250 ms", "Memory — 4 pairs"; close the app fully, reopen: all three scores are still on the board. Save a 4th; it appears at the bottom. Clear: board empties and stays empty after reopening.

90-minute timing: 0–10 plan/sketch — draw the leaderboard, list 3 real scores from his games; 10–20 demo — Rica saves a score and reopens; 20–65 build — TinyDB list save/load blocks; 65–80 test & fix — save 3, close, reopen, clear; 80–90 share — Gin enters his real best scores from Sessions 9–24. Screenshot. Test checklist: Scores survive closing and reopening; new scores appear at once; Clear empties the board permanently; empty boxes do not save a blank score. Common bug: scores vanish after reopening — fix: check the tag is "scores" in both StoreValue and GetValue, and that GetValue's valueIfTagNotThere is an empty list (not empty text). Success check: Gin's leaderboard still shows his scores after the app is closed and reopened. Homework: Play his best game 3 times and save all 3 scores to the leaderboard.

Session 30Notes app — save, view, delete notesWed 9 Jun 2027
Wed 9 Jun 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 9 Jun 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build a notes app that saves typed notes with TinyDB, shows them in a list, opens one to read it, and deletes it. Components: TinyDB1 (non-visible); LabelTitle, Text "My Notes", FontSize 24, FontBold true; TextBoxTitle, Hint "Note title, e.g. Resistor codes"; TextBoxNote, Hint "Write your note here", MultiLine true, Height 120 pixels; ButtonSave, Text "Save note", FontSize 20, BackgroundColor Green; ListView1, Width Fill parent, Height 200 pixels; LabelView, Text "Tap a note to read it", FontSize 20; ButtonDelete, Text "Delete selected", FontSize 18, BackgroundColor Red. Step-by-step build:

1) Designer setup: New project GinNotes. Add TinyDB1 plus the components above.

2) Blocks setup: Create initialize global titles to make a list [], initialize global notes to make a list [], initialize global selectedIndex to 0 (two parallel lists, as in Session 27). Snap when Screen1.Initialize → set global titles to call TinyDB1.GetValue tag "titles" valueIfTagNotThere make a list [] → set global notes to call TinyDB1.GetValue tag "notes" valueIfTagNotThere make a list [] → set ListView1.Elements to get global titles. Make a procedure saveAll: call TinyDB1.StoreValue tag "titles" valueToStore get global titles → call TinyDB1.StoreValue tag "notes" valueToStore get global notes. Snap when ButtonSave.Click → if get TextBoxTitle.Text ≠ "" then add item get TextBoxTitle.Text to list get global titles → add item get TextBoxNote.Text to list get global notes → call saveAll → set ListView1.Elements to get global titles → clear both TextBoxes → else set LabelView.Text to "Give your note a title first!". Snap when ListView1.AfterPicking → set global selectedIndex to get ListView1.SelectionIndex → set LabelView.Text to select list item (get global notes, get global selectedIndex) → set TextBoxTitle.Text to get ListView1.Selection. Snap when ButtonDelete.Click → if get global selectedIndex > 0 then remove list item (list get global titles, index get global selectedIndex) → remove the same index from notes → call saveAll → set ListView1.Elements to get global titles → set LabelView.Text to "Note deleted." → set global selectedIndex to 0.

3) Test: Companion — save "Resistor codes" / "Brown-Black-Red = 1,000 Ω" and "Ohm's Law" / "V = I × R"; tap each title to read it; delete one; close and reopen — the remaining note is still there.

90-minute timing: 0–10 plan/sketch — draw the notes screen, write 2 real notes on paper; 10–20 demo — Rica saves and reopens a note; 20–65 build — parallel lists + TinyDB blocks; 65–80 test & fix — save 3, read 3, delete 1, reopen; 80–90 share — Gin saves his best electronics facts as notes. Screenshot. Test checklist: Saving shows the title in the list at once; tapping a title shows its note; deleting removes title and note together; notes survive closing and reopening. Common bug: tapping a title shows the wrong note — fix: check titles and notes are always changed together (same index added/removed in both) and that AfterPicking uses SelectionIndex on the notes list. Success check: Gin can save, read, delete and reopen notes with nothing lost. Homework: Save 3 real study notes (resistor codes, Ohm's Law, series vs parallel) in the app.

Session 31To-do app — add tasks, mark done, save with TinyDBWed 16 Jun 2027
Wed 16 Jun 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 16 Jun 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build a to-do app that adds tasks, marks the selected one done with a ✓, and saves everything with TinyDB. Components: TinyDB1 (non-visible); LabelTitle, Text "My To-Do List", FontSize 24, FontBold true; TextBoxTask, Hint "New task, e.g. Practise resistor codes"; ButtonAdd, Text "Add task", FontSize 20, BackgroundColor Green; ListView1, Width Fill parent, Height 250 pixels; ButtonDone, Text "✓ Mark done", FontSize 20; ButtonDelete, Text "Delete", FontSize 18; LabelCount, Text "Done: 0 / 0", FontSize 20. Step-by-step build:

1) Designer setup: New project GinTodo. Add TinyDB1 plus the components above.

2) Blocks setup: Create initialize global tasks to make a list [], initialize global selectedIndex to 0. Snap when Screen1.Initialize → set global tasks to call TinyDB1.GetValue tag "tasks" valueIfTagNotThere make a list [] → set ListView1.Elements to get global tasks → call updateCount. Make a procedure saveTasks: call TinyDB1.StoreValue tag "tasks" valueToStore get global tasks. Make a procedure updateCount: count done items with a for each item loop checking starts with (text get item, piece "✓ ") → set LabelCount.Text to join "Done: " + doneCount + " / " + length of list get global tasks. Snap when ButtonAdd.Click → if get TextBoxTask.Text ≠ "" then add item get TextBoxTask.Text to list get global tasks → call saveTasks → set ListView1.Elements to get global tasks → clear TextBoxTask → call updateCount. Snap when ListView1.AfterPicking → set global selectedIndex to get ListView1.SelectionIndex. Snap when ButtonDone.Click → if get global selectedIndex > 0 then set taskText to select list item (tasks, selectedIndex) → if starts with (taskText, "✓ ") then replace list item with (segment taskText, start 3) (un-mark: remove the ✓) → else replace list item (tasks, selectedIndex, replacement join "✓ " + taskText) → call saveTasks → refresh ListView1 → call updateCount. Snap when ButtonDelete.Click → remove the selected index from tasks, save, refresh, updateCount.

3) Test: Companion — add "Practise resistor codes", "Finish quiz app", "Charge phone"; tap the first, Mark done — it shows "✓ Practise resistor codes", Count "Done: 1 / 3"; tap it again — the ✓ comes off. Close and reopen: tasks and ✓ marks are still there.

90-minute timing: 0–10 plan/sketch — write 3 real tasks on paper; 10–20 demo — Rica adds and ticks a task; 20–65 build — TinyDB + done-toggle blocks; 65–80 test & fix — add 3, tick 2, delete 1, reopen; 80–90 share — Gin enters his real homework tasks for the week. Screenshot. Test checklist: Adding shows the task at once; Mark done adds ✓ and updates the count; tapping done again removes ✓; deleting removes only that task; everything survives reopening. Common bug: Mark done adds ✓ to the wrong task — fix: check AfterPicking sets selectedIndex, and that the replace block uses that same index. Success check: Gin can add, tick, untick and delete tasks, and his list survives closing the app. Homework: Add his real tasks for the next week and tick them off as he does them.

Session 32Flashcards — list of questions, flip card, shuffleWed 23 Jun 2027
Wed 23 Jun 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 23 Jun 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build a flashcards app with electronics questions and answers, a tap-to-flip card, Next, and a shuffle button. Components: LabelCard, Text "Tap to flip!", FontSize 28, FontBold true, Height 200 pixels, BackgroundColor Light Gray; ButtonFlip, Text "Flip card", FontSize 20; ButtonNext, Text "Next card", FontSize 18; ButtonShuffle, Text "Shuffle", FontSize 18, BackgroundColor Blue; ButtonPrev, Text "Previous", FontSize 18; LabelCount, Text "Card 1 / 6", FontSize 20; LabelScore, Text "I knew it: 0 Still learning: 0", FontSize 18; ButtonKnew, Text "✓ I knew it", FontSize 18, BackgroundColor Green; ButtonLearning, Text "Still learning", FontSize 18, BackgroundColor Orange. Step-by-step build:

1) Designer setup: New project GinFlashcards. Add the components above; make LabelCard big and centred so it looks like a card.

2) Blocks setup: Create initialize global questions to make a list ["What is V = I × R called?", "Brown-Black-Red = ?", "What is the unit of resistance?", "What does a resistor do?", "Series total of 100 Ω + 200 Ω = ?", "What colour is 1 in resistor codes?"], initialize global answers to make a list ["Ohm's Law", "1,000 Ω", "Ohm (Ω)", "Limits current", "300 Ω", "Brown"], initialize global cardIndex to 1, initialize global showingAnswer to false, initialize global knew to 0, initialize global learning to 0. Make a procedure showCard: set LabelCard.Text to select list item (get global questions, get global cardIndex) → set global showingAnswer to false → set LabelCount.Text to join "Card " + get global cardIndex + " / " + length of list get global questions. Make a procedure flipCard: if get global showingAnswer then set LabelCard.Text to select list item (questions, cardIndex) → set global showingAnswer to false → else set LabelCard.Text to select list item (answers, cardIndex) → set global showingAnswer to true. Snap when ButtonFlip.Click → call flipCard, when LabelCard.Click → call flipCard (tapping the card itself also flips it). Snap when ButtonNext.Click → set global cardIndex to get global cardIndex + 1 → if get global cardIndex > length of list questions then set global cardIndex to 1 → call showCard. Previous: same with - 1, wrapping to the last card at 0. Snap when ButtonKnew.Click → set global knew to get global knew + 1 → update LabelScore → call next-card logic. Snap when ButtonLearning.Click → same for learning. Snap when ButtonShuffle.Click → shuffle both lists together: build two new lists by picking random remaining items — simplest reliable version: set global order to make a list [1,2,3,4,5,6], then repeatedly pick a random index from order, move that question/answer pair into new lists; if that is too long for the session, use a simpler shuffle: swap each position with a random position in both lists at the same time (same random index for questions and answers, so pairs stay matched) → set global cardIndex to 1 → call showCard. Warn explicitly: never shuffle questions without shuffling answers with the same swaps, or questions and answers will mismatch.

3) Test: Companion — card 1 shows the Ohm's Law question; tap Flip — shows "Ohm's Law"; tap Next through all 6 cards; tap Shuffle — cards come in a new order but each question still has its right answer (check Brown-Black-Red still flips to 1,000 Ω); tap "I knew it" twice — score shows 2.

90-minute timing: 0–10 plan/sketch — write 6 Q&A pairs on paper; 10–20 demo — Rica flips 2 cards; 20–65 build — flip + navigation + shuffle blocks; 65–80 test & fix — flip every card, shuffle twice, check pairs still match; 80–90 share — Ray and Run test Gin with the cards. Screenshot. Test checklist: Every card flips question ↔ answer; Next/Previous wrap around at the ends; Shuffle changes the order but never mismatches a Q&A pair; Knew/Learning counts update. Common bug: after Shuffle, a question flips to the wrong answer — fix: check the shuffle swaps the same positions in both the questions and answers lists, every time. Success check: Gin can study all 6 cards, flip, shuffle, and track what he knows — with every answer still matched to its question. Homework: Add 4 more Q&A pairs of his own to the lists.

Session 33Class list — list picker, details screenWed 30 Jun 2027
Wed 30 Jun 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 30 Jun 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build an app that shows a list of electronics parts in a ListPicker and opens a details screen for the item he picks. Components: Screen1 — Label1, Text "My Electronics Parts", FontSize 20, Bold true; ListPicker1, Text "Choose a part"; Label2, Text "", FontSize 16; Button1, Text "Details", FontSize 18; Screen2 ("Details") — Label1, Text "", FontSize 18; Label2, Text "", FontSize 16; Button1, Text "Back", FontSize 18. Step-by-step build:

1) Designer setup: On Screen1 add Label1, ListPicker1, Label2 and Button1. Add a second screen

named "Details" and put two labels and a Back button on it. Keep the layout simple: one column, labels at the top.

2) Blocks setup: In Screen1, make a global variable partsList = make a list with items

"Resistor 220 Ω", "Resistor 1 kΩ", "LED red", "LED green", "Push button", "9 V battery". Set ListPicker1.Elements to get global partsList in when Screen1.Initialize. In when ListPicker1.AfterPicking → set Label2.Text to join "You picked: " + ListPicker1.Selection and set global pickedPart to ListPicker1.Selection. In when Button1.Click → if get global pickedPart ≠ "" then open another screen "Details" with start value get global pickedPart else set Label2.Text to "Pick a part first!".

3) Test: Open the app with Companion, tap ListPicker1, pick "LED red", tap Details, and check the

details screen shows the picked part. 90-minute timing: 0–10 plan/sketch — sketch the two screens on paper, list 6 parts; 10–20 demo — Rica shows a ListPicker opening and a screen opening with a start value; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test every part in the list, fix the empty-pick case; 80–90 share — show Ray and Run the details screen for two different parts. Test checklist: ListPicker opens and shows all 6 parts; picking one updates Label2; Details button with no pick shows "Pick a part first!"; Details screen shows the picked part name; Back returns to Screen1. Common bug: Details screen is blank — fix: check the start value is passed with open another screen with start value and read on Details with get start value in when Details.Initialize → set Label1.Text to get start value. Success check: Gin can pick any part from the list and see its name on the details screen. Homework: Add 4 more parts to partsList and give each one a one-line detail on the Details screen.

Session 34Favourites — star items, save favourites with TinyDBWed 7 Jul 2027
Wed 7 Jul 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 7 Jul 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can star items in a list and save his favourites with TinyDB so they are still there when the app restarts. Components: Screen1 — Label1, Text "Parts — tap ★ to favourite", FontSize 18; ListPicker1, Text "Choose a part"; Button1, Text "★ Favourite", FontSize 18; Button2, Text "Show favourites", FontSize 18; Label2, Text "", FontSize 16; TinyDB1 (non-visible), Namespace "Favourites". Step-by-step build:

1) Designer setup: Add the labels, ListPicker1 and the two buttons. Add TinyDB1 from Storage. Reuse

the parts list from Session 33: "Resistor 220 Ω", "Resistor 1 kΩ", "LED red", "LED green", "Push button", "9 V battery".

2) Blocks setup: Make global variables partsList (the 6 items) and favouritesList = `create

empty list. In when Screen1.Initialize → set ListPicker1.Elements to get global partsList and set global favouritesList to TinyDB1.GetValue tag "favourites" valueIfTagNotThere create empty list. In when ListPicker1.AfterPicking → set global pickedPart to ListPicker1.Selection. In when Button1.Click → if is in list? thing get global pickedPart list get global favouritesList = false then add item to list get global pickedPart list get global favouritesList; call TinyDB1.StoreValue tag "favourites" valueToStore get global favouritesList; set Label2.Text to join get global pickedPart + " ★ saved!" else set Label2.Text to "Already a favourite!". In when Button2.Click → set Label2.Text to join "Favourites: " + get global favouritesList`.

3) Test: Favourite two parts, close the app fully, reopen it, tap "Show favourites" — both must

still be listed. 90-minute timing: 0–10 plan/sketch — decide which parts deserve a star and why; 10–20 demo — Rica shows TinyDB saving one value and loading it after restart; 20–65 build — Designer + Blocks as above; 65–80 test & fix — restart test, duplicate-star test; 80–90 share — show his saved favourites after a full restart. Test checklist: Starring adds the part once only; starring the same part twice shows "Already a favourite!"; favourites survive a full app restart; "Show favourites" lists exactly the starred parts. Common bug: favourites vanish after restart — fix: check TinyDB1.StoreValue runs on every star tap, and GetValue uses the exact same tag "favourites" with valueIfTagNotThere = create empty list. Success check: Gin can star parts, restart the app, and still see his favourites. Homework: Add an "Unfavourite" button that removes the picked part from favouritesList and saves the change.

Session 35Data: sort & filter — sort list A–Z, filter by typeWed 14 Jul 2027
Wed 14 Jul 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 14 Jul 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can sort a list A–Z and filter it by type (resistor, LED, other) using list blocks. Components: Screen1 — Label1, Text "Parts Library", FontSize 20, Bold true; ListView1 (or Label2 to show the list), FontSize 16; Button1, Text "Sort A–Z", FontSize 18; Button2, Text "Show resistors only", FontSize 18; Button3, Text "Show LEDs only", FontSize 18; Button4, Text "Show all", FontSize 18. Step-by-step build:

1) Designer setup: Add Label1, a ListView1 to display the parts, and the four buttons. Use a list

of parts with a type prefix so filtering is simple, e.g. "Resistor: 220 Ω", "Resistor: 1 kΩ", "LED: red", "LED: green", "Button: push", "Battery: 9 V".

2) Blocks setup: Make global variable partsList with the 6 items above and global shownList. In

when Screen1.Initialize → set global shownList to get global partsList and set ListView1.Elements to get global shownList. In when Button1.Click (Sort A–Z) → set global shownList to sort list get global partsList and set ListView1.Elements to get global shownList. In when Button2.Click (resistors) → set global shownList to create empty list, then for each item in list get global partsList → if starts at? text item piece "Resistor" = true then add item to list item list get global shownList, then set ListView1.Elements to get global shownList. Button3 does the same with piece "LED". In when Button4.Click → set global shownList to get global partsList and set ListView1.Elements to get global shownList.

3) Test: Tap each button in turn and check the ListView shows the right items in the right order.

90-minute timing: 0–10 plan/sketch — write the 6 parts with their type prefixes on paper; 10–20 demo — Rica shows sort list and a for each filter on a short list; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test sort, each filter, and Show all; 80–90 share — demo the sorted and filtered views. Test checklist: Sort A–Z puts "Battery: 9 V" first and "Resistor: 1 kΩ" last; resistors filter shows exactly 2 items; LEDs filter shows exactly 2 items; Show all restores all 6. Common bug: filter shows nothing — fix: check the starts at? piece text matches exactly ("Resistor" with capital R) and that shownList is set back into ListView1.Elements after the loop. Success check: Gin can sort the list A–Z and filter it by type with the correct items shown. Homework: Add a "Show buttons & batteries" filter and 2 more parts to the list.

Session 36Quiz with saved progress — resume where you left offWed 21 Jul 2027
Wed 21 Jul 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 21 Jul 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build a quiz that saves his question number and score with TinyDB and resumes where he left off after the app closes. Components: Screen1 — Label1 (question), Text "Question", FontSize 18; Button1, Text "A", FontSize 18; Button2, Text "B", FontSize 18; Button3, Text "C", FontSize 18; Label2 (feedback), Text "", FontSize 16; Label3 (score), Text "Score: 0", FontSize 16; Button4, Text "Restart quiz", FontSize 16; TinyDB1, Namespace "QuizProgress". Step-by-step build:

1) Designer setup: Add the question label, three answer buttons, feedback and score labels, and a

Restart button. Add TinyDB1.

2) Blocks setup: Make global variables questionsList (make a list of 5 questions, e.g. "What does

V stand for in Ohm's Law?", "What is the unit of resistance?", "What colour is the first band of a 220 Ω resistor?"), answersList (make a list of lists, each with 3 options), correctList (make a list of the correct option letters "A", "B", "C"), questionNumber = 1, score = 0. Make a procedure showQuestion: set Label1.Text to select list item list get global questionsList index get global questionNumber, set Button1.Text to select list item list select list item list get global answersList index get global questionNumber index 1, and the same for Button2 (index 2) and Button3 (index 3). In when Screen1.Initialize → set global questionNumber to TinyDB1.GetValue tag "question" valueIfTagNotThere 1 and set global score to TinyDB1.GetValue tag "score" valueIfTagNotThere 0, then call showQuestion and set Label3.Text to join "Score: " + get global score. In when Button1.Click → call checkAnswer "A" (Button2 → "B", Button3 → "C"). Procedure checkAnswer letter: if letter = select list item list get global correctList index get global questionNumber then set global score to get global score + 1; set Label2.Text to "Correct!" else set Label2.Text to "Not quite — try the next one."; then set global questionNumber to get global questionNumber + 1, call TinyDB1.StoreValue tag "question" valueToStore get global questionNumber, call TinyDB1.StoreValue tag "score" valueToStore get global score, if get global questionNumber > length of list get global questionsList then set Label1.Text to join "Quiz done! Score: " + get global score + " / 5" else call showQuestion. In when Button4.Click → set global questionNumber to 1; set global score to 0; store both tags as 0/1; call showQuestion.

3) Test: Answer 2 questions, close the app, reopen — it must show question 3 with the saved score.

90-minute timing: 0–10 plan/sketch — write 5 electronics questions with 3 options each on paper; 10–20 demo — Rica shows saving a number with TinyDB and loading it on open; 20–65 build — Designer + Blocks as above; 65–80 test & fix — restart-resume test, finish-the-quiz test, restart test; 80–90 share — play the quiz from question 3 after a restart. Test checklist: Question and score load correctly after closing and reopening; a correct answer adds 1 to the score; finishing all 5 shows the final score; Restart resets to question 1, score 0. Common bug: quiz always restarts at question 1 — fix: check GetValue tags "question" and "score" match the StoreValue tags exactly, and that loading happens in Screen1.Initialize before showQuestion is called. Success check: Gin can close the quiz halfway, reopen it, and continue from the same question with the same score. Homework: Add 5 more questions to reach 10, with one about series vs parallel resistance.

Session 37Settings screen — theme, sound on/off, saved with TinyDBWed 28 Jul 2027
Wed 28 Jul 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 28 Jul 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build a settings screen where theme (light/dark) and sound on/off are saved with TinyDB and applied when the app opens. Components: Screen1 — Label1, Text "My App", FontSize 20, Bold true; Button1, Text "Settings", FontSize 18; Label2, Text "Welcome!", FontSize 16; Sound1 (non-visible), Source "" (set in Blocks). Screen2 ("Settings") — Label1, Text "Settings", FontSize 20, Bold true; Button1, Text "Theme: Light", FontSize 18; Button2, Text "Sound: On", FontSize 18; Button3, Text "Back", FontSize 18; TinyDB1, Namespace "Settings". Step-by-step build:

1) Designer setup: On Screen1 add the title label, a Settings button and a welcome label, plus

Sound1. On Screen2 ("Settings") add the title label and the three buttons. Add TinyDB1 on Screen1 (TinyDB is shared across screens by its namespace).

2) Blocks setup (Screen1): Make global variables darkTheme = false and soundOn = true. In `when

Screen1.Initialize → set global darkTheme to TinyDB1.GetValue tag "theme" valueIfTagNotThere false, set global soundOn to TinyDB1.GetValue tag "sound" valueIfTagNotThere true, then call applySettings. Procedure applySettings: if get global darkTheme then set Screen1.BackgroundColor to black; set Label1.TextColor to white; set Label2.TextColor to white else set Screen1.BackgroundColor to white; set Label1.TextColor to black; set Label2.TextColor to black. In when Button1.Click → open another screen "Settings". Blocks setup (Settings screen): In when Settings.Initialize → read the same two tags from TinyDB1 and set Button1.Text to "Theme: Dark" or "Theme: Light" and Button2.Text to "Sound: On" or "Sound: Off". In when Button1.Click → set global darkTheme to not get global darkTheme; call TinyDB1.StoreValue tag "theme" valueToStore get global darkTheme; update Button1.Text. In when Button2.Click → set global soundOn to not get global soundOn; call TinyDB1.StoreValue tag "sound" valueToStore get global soundOn; update Button2.Text. In when Button3.Click → close screen. Back on Screen1, add when Screen1.OtherScreenClosed → call applySettings` so the theme updates on return.

3) Test: Switch to dark theme, turn sound off, close the app, reopen — dark theme must still

apply. 90-minute timing: 0–10 plan/sketch — sketch both screens and the two settings; 10–20 demo — Rica shows a toggle button flipping true/false and saving it; 20–65 build — Designer + Blocks as above; 65–80 test & fix — restart test for both settings; 80–90 share — demo light vs dark and explain where each setting is stored. Test checklist: Theme button flips Light/Dark and the label updates; sound button flips On/Off; both settings survive a full restart; returning from Settings applies the new theme at once. Common bug: theme changes on the Settings screen but not on Screen1 — fix: check Screen1.OtherScreenClosed calls applySettings, and that both screens use the same TinyDB namespace "Settings" and the same tags "theme" and "sound". Success check: Gin can change theme and sound, restart the app, and find both settings exactly as he left them. Homework: Add a third setting — a "Big text" toggle that sets Label font sizes to 22 when on.

Session 38Data app 1: resistor log — log resistors, view historyWed 4 Aug 2027
Wed 4 Aug 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 4 Aug 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build a resistor log that records each resistor he measures (value, bands) and shows the full history, saved with TinyDB. Components: Screen1 — Label1, Text "Resistor Log", FontSize 20, Bold true; TextBox1, Hint "Value, e.g. 220 Ω", FontSize 16; TextBox2, Hint "Bands, e.g. red red brown", FontSize 16; Button1, Text "Save resistor", FontSize 18; Button2, Text "Clear history", FontSize 16; ListView1, FontSize 16; Label2, Text "", FontSize 16; TinyDB1, Namespace "ResistorLog". Step-by-step build:

1) Designer setup: Add the title label, two TextBoxes, Save and Clear buttons, a ListView for

history and a status label. Add TinyDB1.

2) Blocks setup: Make global variable resistorLog = create empty list. In `when

Screen1.Initialize → set global resistorLog to TinyDB1.GetValue tag "log" valueIfTagNotThere create empty list and set ListView1.Elements to get global resistorLog. In when Button1.Click → if TextBox1.Text ≠ "" and TextBox2.Text ≠ "" then add item to list join TextBox1.Text + " Ω — " + TextBox2.Text list get global resistorLog; call TinyDB1.StoreValue tag "log" valueToStore get global resistorLog; set ListView1.Elements to get global resistorLog; set TextBox1.Text to ""; set TextBox2.Text to ""; set Label2.Text to "Saved!" else set Label2.Text to "Fill in both boxes first!". In when Button2.Click → set global resistorLog to create empty list; call TinyDB1.StoreValue tag "log" valueToStore get global resistorLog; set ListView1.Elements to get global resistorLog; set Label2.Text to "History cleared."`.

3) Test: Save three resistors (e.g. 220 Ω red-red-brown, 1 kΩ brown-black-red, 10 kΩ

brown-black-orange), close and reopen — all three must still be listed. 90-minute timing: 0–10 plan/sketch — list 3 real resistors to log, with bands; 10–20 demo — Rica shows adding one text item to a TinyDB-saved list; 20–65 build — Designer + Blocks as above; 65–80 test & fix — save, restart, clear tests; 80–90 share — show the history list and read back the bands for one resistor. Test checklist: Saving with both boxes filled adds one row to the ListView; saving with an empty box shows the warning and adds nothing; history survives a restart; Clear empties the list and the saved data. Common bug: history disappears after restart — fix: check StoreValue runs after every save and that Initialize loads tag "log" into ListView1.Elements. Success check: Gin can log resistors and see the full history after reopening the app. Homework: Add a third TextBox for "Where used" (e.g. "LED circuit") and include it in each log row.

Session 39Data app 2: measurement log — record voltage / current, view listWed 11 Aug 2027
Wed 11 Aug 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 11 Aug 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can build a measurement log that records voltage and current readings, calculates power (P = V × I) for each row, and shows the saved list. Components: Screen1 — Label1, Text "Measurement Log", FontSize 20, Bold true; TextBox1, Hint "Voltage (V)", NumbersOnly true; TextBox2, Hint "Current (A)", NumbersOnly true; Button1, Text "Save reading", FontSize 18; Button2, Text "Clear log", FontSize 16; ListView1, FontSize 16; Label2, Text "Total power: 0 W", FontSize 16; TinyDB1, Namespace "MeasureLog". Step-by-step build:

1) Designer setup: Add the title label, two number TextBoxes, Save and Clear buttons, a ListView

and a total-power label. Add TinyDB1.

2) Blocks setup: Make global variables measureLog = create empty list and totalPower = 0. In

when Screen1.Initialize → set global measureLog to TinyDB1.GetValue tag "readings" valueIfTagNotThere create empty list, set ListView1.Elements to get global measureLog, then set global totalPower to 0 and for each item in list get global measureLog — this needs the power stored in the row, so store each row as text "V=5, I=0.5, P=2.5 W" (see next step) and recompute the total by re-adding: simpler — keep a second saved value: set global totalPower to TinyDB1.GetValue tag "totalPower" valueIfTagNotThere 0 and set Label2.Text to join "Total power: " + get global totalPower + " W". In when Button1.Click → if TextBox1.Text ≠ "" and TextBox2.Text ≠ "" then set local variable power to TextBox1.Text × TextBox2.Text; add item to list join "V=" + TextBox1.Text + " V, I=" + TextBox2.Text + " A, P=" + power + " W" list get global measureLog; set global totalPower to get global totalPower + power; call TinyDB1.StoreValue tag "readings" valueToStore get global measureLog; call TinyDB1.StoreValue tag "totalPower" valueToStore get global totalPower; set ListView1.Elements to get global measureLog; set Label2.Text to join "Total power: " + get global totalPower + " W"; set TextBox1.Text to ""; set TextBox2.Text to "" else set Label2.Text to "Enter both voltage and current!". In when Button2.Click → set global measureLog to create empty list; set global totalPower to 0; store both tags; set ListView1.Elements to create empty list; set Label2.Text to "Total power: 0 W".

3) Test: Enter V=5, I=0.5 (expect P=2.5 W), then V=9, I=0.2 (expect P=1.8 W, total 4.3 W). Close

and reopen — both rows and the total must still be there. 90-minute timing: 0–10 plan/sketch — write 3 sample readings on paper and work out P = V × I for each; 10–20 demo — Rica shows the maths block multiplying two TextBox numbers; 20–65 build — Designer + Blocks as above; 65–80 test & fix — check the power maths, restart test, clear test; 80–90 share — read back the log and explain what total power means. Test checklist: Each saved row shows V, I and the correct P; the total power adds up across rows; the log and total survive a restart; Clear resets both to empty/0. Common bug: power shows as text joined together, e.g. "50.5" instead of 2.5 — fix: make sure the multiply block uses the two TextBox values as numbers (NumbersOnly on both TextBoxes) and that the + for total power is a maths +, not a text join. Success check: Gin can record voltage and current, see the correct power per row, and keep a running total that survives a restart. Homework: Add a TextBox for resistance R and show the expected current I = V ÷ R beside each row.

Session 40Data showcase — test all saved-data apps, fix lost-data bugsWed 18 Aug 2027
Wed 18 Aug 2027 | Phase 3 — Data, Lists & Storage (TinyDB)

Date: Wed 18 Aug 2027 | Phase: Phase 3 — Data, Lists & Storage (TinyDB) Learning objective: Gin can test every Phase 3 saved-data app (notes, to-do, flashcards, favourites, quiz progress, settings, resistor log, measurement log), find lost-data bugs, and fix them. Components: No new app — reuse the Session 25–39 apps on the phone. One checklist on paper (or a Label in a simple "Showcase" app): Label1, Text "Phase 3 Showcase Checklist", FontSize 20, Bold true; ListView1 with the 8 app names; Label2, Text "", FontSize 16. Step-by-step build:

1) Designer setup: No new Designer work — open each saved project in App Inventor (Notes, To-do,

Flashcards, Favourites, Quiz, Settings, Resistor Log, Measurement Log) and list them in the paper checklist with two columns: "Saves?" and "Loads after restart?".

2) Blocks setup: For each app, run the same test routine: (a) add one new item / change one

setting, (b) close the app fully (swipe it away, not just Home), (c) reopen and check the change is still there. For any app that fails, open its Blocks and check the three TinyDB rules: StoreValue runs on every change, GetValue runs in Screen1.Initialize, and the tag string is identical in both places (same spelling, same capitals). Fix the tag or the missing StoreValue, then retest. Keep a bug list on paper: app name, what was lost, what the fix was.

3) Test: Finish with a demo round — Gin shows Ray, Run and Rica one saved item in each app after

a restart. 90-minute timing: 0–10 plan/sketch — write the 8-app checklist and the test routine; 10–20 demo — Rica demos the full close-and-reopen test on one app; 20–65 build — test all 8 apps, fix bugs as found; 65–80 test & fix — retest every fixed app once more; 80–90 share — demo round: one saved item per app, plus the bug list. Test checklist: Every app keeps its data after a full close and reopen; every fixed bug is retested and passes; the bug list records each fix. Common bug: a tag spelled differently in StoreValue vs GetValue (e.g. "favourites" vs "Favorites") — fix: pick one spelling, change the other block to match, then save one item again and retest after a restart. Success check: Gin can prove all 8 Phase 3 apps keep their data after a restart and explain the three TinyDB rules. Homework: Pick the best Phase 3 app and write down two improvements to build next time.

Session 41Accelerometer 2 — tilt maze, live X / Y displayWed 25 Aug 2027
Wed 25 Aug 2027 | Phase 4 — Sensors & Media

Date: Wed 25 Aug 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build a tilt maze where a ball moves with the phone's accelerometer and the live X and Y values are shown on screen. Components: Screen1 — Canvas1, Width Fill parent, Height 400 pixels; Ball1 (Sprite on Canvas1), Heading 0, Interval 50, Speed 0; Label1, Text "X: 0 Y: 0", FontSize 18; Label2, Text "Tilt to reach the green square!", FontSize 16; Button1, Text "Reset ball", FontSize 18; AccelerometerSensor1 (non-visible), Enabled true. Step-by-step build:

1) Designer setup: Add Canvas1, then add Ball1 as a sprite on it (draw a small circle image or use

the built-in ball shape, Radius 15). Add the two labels and the Reset button. Add AccelerometerSensor1. Draw the maze on the canvas background: use the Canvas background colour and add a green target rectangle by drawing it in Blocks at start (or place a second sprite as the target).

2) Blocks setup: Make global variables ballX = 100 and ballY = 100. In `when

Screen1.Initialize → set Ball1.X to 100; set Ball1.Y to 100 and call Canvas1.DrawShape or place a green target sprite at X 250, Y 300. In when AccelerometerSensor1.AccelerationChanged xAccel yAccel zAccel → set Label1.Text to join "X: " + round xAccel + " Y: " + round yAccel, set Ball1.X to Ball1.X + xAccel × 5, set Ball1.Y to Ball1.Y + yAccel × 5, then keep the ball inside the canvas: if Ball1.X < 0 then set Ball1.X to 0; if Ball1.X > Canvas1.Width - 30 then set Ball1.X to Canvas1.Width - 30 (same for Y with Canvas1.Height). In when Ball1.CollidedWith targetSprite (or when the ball reaches the target area: if Ball1.X > 240 and Ball1.Y > 290 then set Label2.Text to "You win! 🎉") — use the simple position check so it works without a second sprite. In when Button1.Click → set Ball1.X to 100; set Ball1.Y to 100; set Label2.Text to "Tilt to reach the green square!"`.

3) Test: Hold the phone flat, tilt slowly left/right and up/down, and watch the ball move and the

X/Y numbers change. Reach the target to win. 90-minute timing: 0–10 plan/sketch — sketch the maze and the target square on paper; 10–20 demo — Rica shows the X/Y numbers changing as she tilts the phone; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test on the real phone (the emulator has no tilt), tune the × 5 speed; 80–90 share — race Ray and Run to the target square. Test checklist: X and Y numbers change live when the phone tilts; the ball moves in the tilt direction; the ball cannot leave the canvas; reaching the target shows "You win!"; Reset puts the ball back at the start. Common bug: ball moves the wrong way or too fast — fix: swap the sign (- xAccel instead of + xAccel) or lower the multiplier from 5 to 3; note that the accelerometer does nothing in the emulator, so always test on the phone with Companion. Success check: Gin can steer the ball to the target by tilting the phone while the live X/Y values update. Homework: Add a second target square and a timer that shows how many seconds the maze took.

Session 42Orientation — tilt to steer, screen colour by tiltWed 1 Sep 2027
Wed 1 Sep 2027 | Phase 4 — Sensors & Media

Date: Wed 1 Sep 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can use the OrientationSensor to steer a car sprite by tilting and change the screen colour based on the tilt angle. Components: Screen1 — Canvas1, Width Fill parent, Height 400 pixels; Car1 (Sprite on Canvas1), Interval 50, Speed 0; Label1, Text "Roll: 0° Pitch: 0°", FontSize 18; Label2, Text "Tilt to steer!", FontSize 16; Button1, Text "Reset", FontSize 18; OrientationSensor1 (non-visible), Enabled true. Step-by-step build:

1) Designer setup: Add Canvas1 and Car1 (a small rectangle or car image sprite, Width 40, Height

25). Add the two labels and the Reset button. Add OrientationSensor1.

2) Blocks setup: In when OrientationSensor1.OrientationChanged azimuth pitch roll → `set

Label1.Text to join "Roll: " + round roll + "° Pitch: " + round pitch + "°", then steer: set Car1.X to Car1.X + roll × 2 and set Car1.Y to Car1.Y + pitch × 2, then clamp the car inside the canvas (same if checks as Session 41). Then colour by tilt: if absolute value of roll > 30 then set Screen1.BackgroundColor to red else if absolute value of roll > 15 then set Screen1.BackgroundColor to yellow else set Screen1.BackgroundColor to green. In when Button1.Click → set Car1.X to Canvas1.Width ÷ 2; set Car1.Y to Canvas1.Height ÷ 2; set Screen1.BackgroundColor to white`.

3) Test: Tilt the phone gently — the car should drift, and the screen should turn green (gentle),

yellow (medium) or red (steep tilt). 90-minute timing: 0–10 plan/sketch — sketch the car, the tilt directions and the three colours; 10–20 demo — Rica shows roll/pitch numbers changing on the phone; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test on the phone, tune the × 2 speed and the 15°/30° limits; 80–90 share — steer the car in a figure-of-eight without going red. Test checklist: Roll and pitch numbers update live; the car moves with the tilt; the screen turns green/yellow/red at the right tilt amounts; Reset centres the car and restores a white screen. Common bug: colours flicker or never change — fix: check the if / else if order (test > 30 first, then > 15) and that the values compared are the roll from the event, not a stale variable; test on the phone, not the emulator. Success check: Gin can steer the car by tilt and explain what green, yellow and red mean. Homework: Add a "steep tilt" counter that adds 1 each time the screen turns red.

Session 43Sound sensor — clap / loud sound triggers an actionWed 8 Sep 2027
Wed 8 Sep 2027 | Phase 4 — Sensors & Media

Date: Wed 8 Sep 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build an app that listens with the SoundSensor (via the microphone) and triggers an action — a light, a sound, a counter — when it hears a clap or loud sound. Components: Screen1 — Label1, Text "Clap to light the LED!", FontSize 20, Bold true; Label2, Text "Sound level: 0", FontSize 18; Button1 (the "LED"), Text "● OFF", FontSize 24, BackgroundColor gray; Button2, Text "Reset claps", FontSize 16; Label3, Text "Claps: 0", FontSize 16; SoundRecorder1 (non-visible, used only as the microphone source) — note: App Inventor has no built-in SoundSensor component; the working approach is the SoundRecorder + a loudness check is not built in either, so this session uses the practical blocks-only method below. Step-by-step build:

1) Designer setup: Add the labels, the big LED button (Button1) and the Reset button. Note for

Rica: App Inventor has no SoundSensor component with a live loudness reading. The honest blocks-only method is: use a Clock timer plus a SoundRecorder recording, or — simpler and reliable in class — use a "clap" button to simulate the trigger while learning the trigger logic, then test the real microphone path below.

2) Blocks setup (trigger logic, the core of the session): Make global variables clapCount = 0 and

ledOn = false. Make a procedure onLoudSound: set global clapCount to get global clapCount + 1; set Label3.Text to join "Claps: " + get global clapCount; if get global ledOn = false then set global ledOn to true; set Button1.Text to "● ON"; set Button1.BackgroundColor to yellow else set global ledOn to false; set Button1.Text to "● OFF"; set Button1.BackgroundColor to gray. Then wire the trigger: when Button1.Click → call onLoudSound (this is the test trigger — a tap stands in for a clap while building). For the real microphone path: add SoundRecorder1, and in when Button2.Click (label it "Listen") → call SoundRecorder1.Start; in when SoundRecorder1.AfterSoundRecorded sound → call onLoudSound and set Label2.Text to "Heard a sound!". Explain plainly to Gin: the recorder fires when a recording finishes, not at the exact loudness peak, so a true live loudness meter is not available in blocks — the app reacts to a recorded sound, and the toggle logic is the same as a real clap switch.

3) Test: Tap the LED button — it must toggle ON/OFF and the clap counter must go up by 1 each

time. Then test the Listen path: tap Listen, clap once, stop the recording, and check the counter goes up. 90-minute timing: 0–10 plan/sketch — sketch the LED and the clap counter; 10–20 demo — Rica shows the toggle logic with a button first, then the recorder path; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test both trigger paths, check the counter; 80–90 share — demo the clap counter to Ray and Run and explain the loudness limit honestly. Test checklist: Tapping toggles the LED and adds 1 to the counter; the recorder path also triggers the toggle; Reset sets claps to 0 and the LED off. Common bug: the counter goes up twice per clap — fix: check onLoudSound is called from only one place at a time (remove the Button1 test trigger once the recorder path works, or keep the button and treat it as the manual test only). Success check: Gin can explain what his app does when it hears a sound, and state plainly that App Inventor has no live loudness sensor in blocks. Homework: Add a second action — when the LED turns on, also play a short sound with the Player component.

Session 44Camera app — take photo, show it in the appWed 15 Sep 2027
Wed 15 Sep 2027 | Phase 4 — Sensors & Media

Date: Wed 15 Sep 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build an app that opens the phone camera, takes a photo, and shows it in the app. Components: Screen1 — Label1, Text "My Camera", FontSize 20, Bold true; Button1, Text "Take photo", FontSize 18; Image1, Width Fill parent, Height 300 pixels, Picture "" (empty); Label2, Text "", FontSize 16; Button2, Text "Clear photo", FontSize 16; Camera1 (non-visible). Step-by-step build:

1) Designer setup: Add the title label, the Take photo button, Image1 (leave Picture empty), the

status label and the Clear button. Add Camera1 from Media.

2) Blocks setup: In when Button1.Click → call Camera1.TakePicture. In `when

Camera1.AfterPicture image → set Image1.Picture to image; set Label2.Text to "Photo saved!". In when Button2.Click → set Image1.Picture to ""; set Label2.Text to "Photo cleared."`.

3) Test: Tap Take photo, take a picture of something on the desk (e.g. a resistor), and check it

appears in Image1. Tap Clear and check the image disappears. 90-minute timing: 0–10 plan/sketch — sketch the screen: button on top, photo below; 10–20 demo — Rica takes one photo and shows where it appears; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test on the real phone (the emulator camera may not work), check the photo is the right way up; 80–90 share — photograph a resistor and show it in the app. Test checklist: Take photo opens the camera; the photo appears in Image1 after taking it; Clear empties the image; the app does not crash if the camera is cancelled. Common bug: nothing appears after taking the photo — fix: check Camera1.AfterPicture sets Image1.Picture to the image value from the event (not a fixed file name), and test on a real phone with Companion, since the emulator often has no working camera. Success check: Gin can take a photo and see it inside his own app. Homework: Add a second Image and a button "Take photo 2" so the app can show two photos side by side.

Session 45Photo gallery — save photos, view in a listWed 22 Sep 2027
Wed 22 Sep 2027 | Phase 4 — Sensors & Media

Date: Wed 22 Sep 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build a photo gallery that saves photo file paths with TinyDB and shows the saved photos in a list to tap and view. Components: Screen1 — Label1, Text "Photo Gallery", FontSize 20, Bold true; Button1, Text "Take photo", FontSize 18; ListView1, FontSize 16; Image1, Width Fill parent, Height 300 pixels, Picture ""; Label2, Text "", FontSize 16; TinyDB1, Namespace "PhotoGallery"; Camera1 (non-visible). Step-by-step build:

1) Designer setup: Add the title label, Take photo button, ListView1 (shows photo names), Image1

(shows the selected photo), and the status label. Add Camera1 and TinyDB1.

2) Blocks setup: Make global variables photoList = create empty list and photoCount = 0. In

when Screen1.Initialize → set global photoList to TinyDB1.GetValue tag "photos" valueIfTagNotThere create empty list, set global photoCount to TinyDB1.GetValue tag "count" valueIfTagNotThere 0, set ListView1.Elements to get global photoList. In when Button1.Click → call Camera1.TakePicture. In when Camera1.AfterPicture image → set global photoCount to get global photoCount + 1; add item to list join "Photo " + get global photoCount list get global photoList; call TinyDB1.StoreValue tag "photos" valueToStore get global photoList; call TinyDB1.StoreValue tag "count" valueToStore get global photoCount; set ListView1.Elements to get global photoList; set Label2.Text to join "Saved photo " + get global photoCount. Note: App Inventor's Camera.AfterPicture gives a file path, and TinyDB can only store that path text, not the image itself — so also keep a second list photoPaths saved under tag "paths" with the image value added in the same step. In when ListView1.AfterPicking → set Image1.Picture to select list item list get global photoPaths index ListView1.SelectionIndex; set Label2.Text to ListView1.Selection.

3) Test: Take 3 photos, tap each name in the ListView, and check the right photo shows in Image1.

Close and reopen — the names must still be listed. 90-minute timing: 0–10 plan/sketch — sketch the gallery: list on top, photo below; 10–20 demo — Rica shows one photo saved and reloaded from a list; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test 3 photos, tap each, restart test; 80–90 share — show the gallery of 3 photos to Ray and Run. Test checklist: Each new photo adds one name to the list; tapping a name shows that photo; names survive a restart; photos are the right ones (check order matches). Common bug: tapping a name shows the wrong photo or nothing — fix: check photoList (names) and photoPaths (file paths) are added in the same order and both saved with TinyDB, and that AfterPicking uses SelectionIndex on the paths list. Note: if the phone's storage is cleared, saved photo files may disappear even though the names remain — that is a phone storage limit, not a code bug. Success check: Gin can take photos, see them listed, tap a name to view it, and find the list still there after a restart. Homework: Add a "Delete photo" button that removes the selected name and path from both lists and saves the change.

Session 46Sound recorder — record, play back, save nameWed 29 Sep 2027
Wed 29 Sep 2027 | Phase 4 — Sensors & Media

Date: Wed 29 Sep 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build a sound recorder that records his voice, plays it back, and saves the recording with a name in a list. Components: Screen1 — Label1, Text "Sound Recorder", FontSize 20, Bold true; TextBox1, Hint "Recording name, e.g. hello", FontSize 16; Button1, Text "● Record", FontSize 18; Button2, Text "■ Stop", FontSize 18; Button3, Text "▶ Play", FontSize 18; ListView1, FontSize 16; Label2, Text "", FontSize 16; SoundRecorder1 (non-visible); Player1 (non-visible), Source ""; TinyDB1, Namespace "Recordings". Step-by-step build:

1) Designer setup: Add the title label, the name TextBox, Record/Stop/Play buttons, ListView1 for

saved recordings and the status label. Add SoundRecorder1, Player1 and TinyDB1.

2) Blocks setup: Make global variables recordingList = create empty list and recordingPaths =

create empty list and lastSound = "". In when Screen1.Initialize → load both lists from TinyDB1 (tags "names" and "paths", valueIfTagNotThere create empty list) and set ListView1.Elements to get global recordingList. In when Button1.Click → call SoundRecorder1.Start; set Label2.Text to "Recording… speak now!". In when Button2.Click → call SoundRecorder1.Stop; set Label2.Text to "Recording stopped.". In when SoundRecorder1.AfterSoundRecorded sound → set global lastSound to sound; if TextBox1.Text = "" then set TextBox1.Text to join "Recording " + length of list get global recordingList + 1; add item to list TextBox1.Text list get global recordingList; add item to list sound list get global recordingPaths; call TinyDB1.StoreValue tag "names" valueToStore get global recordingList; call TinyDB1.StoreValue tag "paths" valueToStore get global recordingPaths; set ListView1.Elements to get global recordingList; set Label2.Text to join "Saved: " + TextBox1.Text. In when Button3.Click → if get global lastSound ≠ "" then set Player1.Source to get global lastSound; call Player1.Start; set Label2.Text to "Playing…" else set Label2.Text to "Record something first!". In when ListView1.AfterPicking → set global lastSound to select list item list get global recordingPaths index ListView1.SelectionIndex; set Label2.Text to join "Selected: " + ListView1.Selection + " — tap Play".

3) Test: Record "Hello, this is Gin", stop, play it back, then record a second one and play it from

the list. 90-minute timing: 0–10 plan/sketch — list 3 things to record (e.g. his name, "V = I × R", a resistor colour code); 10–20 demo — Rica records one short clip and plays it back; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test record/stop/play and the list; 80–90 share — play back his best recording for Ray and Run. Test checklist: Record starts and stops cleanly; Play plays the last recording; the list shows each saved name; tapping a list item then Play plays that recording; names survive a restart. Common bug: Play does nothing — fix: check Player1.Source is set to the sound file path from AfterSoundRecorded (or the selected path) before Player1.Start is called, and that the path is not empty. Success check: Gin can record, name, save, and play back his own voice recordings from a list. Homework: Record the resistor colour code chant (black, brown, red, orange…) and save it as "Colour codes".

Session 47Text-to-speech — type text, app speaks itWed 6 Oct 2027
Wed 6 Oct 2027 | Phase 4 — Sensors & Media

Date: Wed 6 Oct 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build an app that speaks any text he types, using the TextToSpeech component. Components: Screen1 — Label1, Text "Talking App", FontSize 20, Bold true; TextBox1, Hint "Type something for the app to say", FontSize 16; Button1, Text "▶ Speak", FontSize 18; Button2, Text "■ Stop", FontSize 16; Button3, Text "Say Ohm's Law", FontSize 16; Label2, Text "", FontSize 16; TextToSpeech1 (non-visible), Language "en", Pitch 1.0, SpeechRate 1.0. Step-by-step build:

1) Designer setup: Add the title label, the TextBox, Speak/Stop buttons, the Ohm's Law shortcut

button and the status label. Add TextToSpeech1.

2) Blocks setup: In when Button1.Click → `if TextBox1.Text ≠ "" then call TextToSpeech1.Speak

message TextBox1.Text; set Label2.Text to join "Saying: " + TextBox1.Text else set Label2.Text to "Type something first!". In when Button2.Click → call TextToSpeech1.Stop — note: App Inventor's TextToSpeech has no Stop block in the standard component, so use this honest alternative: set a global speaking flag is not needed; instead make Button2 say the next short phrase, or simply leave Button2 as "Clear text" → set TextBox1.Text to ""; set Label2.Text to "". Keep the button but label it honestly in the Designer as "Clear". In when Button3.Click → call TextToSpeech1.Speak message "V equals I times R. Voltage equals current times resistance."; set Label2.Text to "Saying Ohm's Law"`. Optional: add a second shortcut button "Say colour codes" that speaks "Black, brown, red, orange, yellow, green, blue, violet, grey, white."

3) Test: Type "Hello, I am Gin", tap Speak, and listen. Then tap "Say Ohm's Law" and check it

speaks the formula. 90-minute timing: 0–10 plan/sketch — write 3 sentences for the app to say; 10–20 demo — Rica types one sentence and the phone speaks it; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test typed text and both shortcut buttons, check the volume is up; 80–90 share — make the app say his name and Ohm's Law for Ray and Run. Test checklist: Typed text is spoken aloud; empty text shows the warning instead of speaking; the Ohm's Law button speaks the formula; Clear empties the TextBox. Common bug: nothing is heard — fix: check the phone volume and that TextToSpeech1 Language is "en" (or "th" for Thai text); also note the emulator usually has no speech, so test on the real phone with Companion. Success check: Gin can type any sentence and hear the app speak it, plus speak Ohm's Law from a shortcut button. Homework: Add a button that speaks the resistor colour code order from memory.

Session 48Speech recognizer — speak, app shows the words (exploration)Wed 13 Oct 2027
Wed 13 Oct 2027 | Phase 4 — Sensors & Media

Date: Wed 13 Oct 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build an app that listens to his voice and shows the recognised words on screen, and can explain that recognition is not always accurate. Components: Screen1 — Label1, Text "Speak to Me", FontSize 20, Bold true; Button1, Text "🎤 Listen", FontSize 18; Label2, Text "Tap Listen, then speak…", FontSize 18; Label3, Text "", FontSize 16; Button2, Text "Clear", FontSize 16; SpeechRecognizer1 (non-visible). Step-by-step build:

1) Designer setup: Add the title label, the Listen button, the result label (Label2, large), the

status label (Label3) and the Clear button. Add SpeechRecognizer1 from Media.

2) Blocks setup: In when Button1.Click → `call SpeechRecognizer1.GetText; set Label3.Text to

"Listening…". In when SpeechRecognizer1.AfterGettingText result partial → set Label2.Text to result; set Label3.Text to "Heard you!". In when SpeechRecognizer1.BeforeGettingText → set Label3.Text to "Listening…". In when Button2.Click → set Label2.Text to "Tap Listen, then speak…"; set Label3.Text to "". Add a fun check: if result contains "ohm" (use the text contains block on Label2.Text) then set Label3.Text to "You said Ohm's Law!" — put this inside AfterGettingText` after setting Label2.

3) Test: Tap Listen, say "Hello Gin" clearly, and check the words appear. Then say "Ohm's Law" and

check the special message appears. Try a Thai word and see what happens. 90-minute timing: 0–10 plan/sketch — write 5 test phrases (his name, "Ohm's Law", "resistor", a Thai word, a number); 10–20 demo — Rica speaks one phrase and shows the result, including one misheard word; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test each phrase, note which ones are misheard; 80–90 share — demo the app and read out its mistakes honestly. Test checklist: Listen opens the microphone prompt; spoken words appear in Label2; the "ohm" check fires when he says Ohm's Law; Clear resets the screen; the app does not crash if he says nothing. Common bug: nothing appears, or the app closes the listening prompt at once — fix: check the phone has internet (recognition needs it) and microphone permission is allowed for the Companion app; speak clearly and wait for the prompt before talking. Note: this is labelled exploration because recognition accuracy varies, it needs internet, and results differ between phones. Success check: Gin can speak and see his words on screen, and can name two phrases the recognizer got wrong and why. Homework: Test the app with 3 electronics words (resistor, voltage, current) and write down exactly what it heard for each.

Session 49Video player — play a video, controlsWed 20 Oct 2027
Wed 20 Oct 2027 | Phase 4 — Sensors & Media

Date: Wed 20 Oct 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build an app that plays a video with Play, Pause and Stop controls and shows the video's position. Components: Screen1 — Label1, Text "Video Player", FontSize 20, Bold true; VideoPlayer1, Width Fill parent, Height 300 pixels, Source "" (set in Blocks or Designer to a sample video); Button1, Text "▶ Play", FontSize 18; Button2, Text "⏸ Pause", FontSize 18; Button3, Text "■ Stop", FontSize 18; Label2, Text "Position: 0 s", FontSize 16; Clock1 (non-visible), TimerInterval 1000, TimerEnabled false. Step-by-step build:

1) Designer setup: Add the title label, VideoPlayer1, the three control buttons and the position

label. Add Clock1 with TimerEnabled false. For the video file: use a short sample video already on the phone, or a video Gin recorded earlier — set VideoPlayer1.Source to that file name in the Designer (e.g. a clip in the phone's storage). If no video is on the phone, record a 10-second clip with the phone's camera app first and use that file.

2) Blocks setup: In when Button1.Click → `call VideoPlayer1.Start; set Clock1.TimerEnabled to

true; set Label2.Text to "Playing…". In when Button2.Click → call VideoPlayer1.Pause; set Clock1.TimerEnabled to false. In when Button3.Click → call VideoPlayer1.Stop; set Clock1.TimerEnabled to false; set Label2.Text to "Position: 0 s". In when Clock1.Timer → set Label2.Text to join "Position: " + round VideoPlayer1.CurrentPosition ÷ 1000 + " s". In when VideoPlayer1.Completed → set Clock1.TimerEnabled to false; set Label2.Text to "Finished!"`.

3) Test: Play the video, pause halfway and check the position label freezes, resume, then let it

finish and check "Finished!" appears. 90-minute timing: 0–10 plan/sketch — pick the video to play and sketch the controls; 10–20 demo — Rica plays a clip and shows Pause freezing the position; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test all three buttons and the finish message; 80–90 share — play his video for Ray and Run with the controls. Test checklist: Play starts the video; Pause freezes both video and position label; Stop resets to the start; the position label counts up in seconds; the finish message appears at the end. Common bug: the video plays but the position label never changes — fix: check Clock1.TimerEnabled is set to true in the Play button and that the Timer block reads VideoPlayer1.CurrentPosition (milliseconds, so divide by 1000 for seconds). Success check: Gin can play, pause and stop a video and read its position in seconds. Homework: Add a "Replay" button that stops the video and starts it again from the beginning.

Session 50Drawing app — canvas, colours, clear, save drawingWed 27 Oct 2027
Wed 27 Oct 2027 | Phase 4 — Sensors & Media

Date: Wed 27 Oct 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build a drawing app where he picks a colour, draws on a canvas with his finger, clears it, and saves the drawing. Components: Screen1 — Canvas1, Width Fill parent, Height 400 pixels, BackgroundColor white; Button1, Text "Red", BackgroundColor red, FontSize 16; Button2, Text "Blue", BackgroundColor blue, FontSize 16; Button3, Text "Green", BackgroundColor green, FontSize 16; Button4, Text "Black", BackgroundColor black, FontSize 16; Button5, Text "Clear", FontSize 16; Button6, Text "Save drawing", FontSize 16; Label1, Text "Colour: black", FontSize 16. Step-by-step build:

1) Designer setup: Add Canvas1 and a row of colour buttons, then Clear and Save buttons and the

colour label. Set each colour button's BackgroundColor to its colour.

2) Blocks setup: Make global variable penColour = black (use the colour block). In `when

Button1.Click → set global penColour to red; set Label1.Text to "Colour: red" (Button2 → blue, Button3 → green, Button4 → black). In when Canvas1.Dragged startX startY prevX prevY currentX currentY → call Canvas1.DrawLine x1 prevX y1 prevY x2 currentX y2 currentY — then set the line colour and width: App Inventor's DrawLine uses the canvas PaintColor and LineWidth, so before the draw call add set Canvas1.PaintColor to get global penColour and set Canvas1.LineWidth to 5. In when Canvas1.Touched x y → call Canvas1.DrawCircle x x y y r 5 fill true (a dot where he taps). In when Button5.Click → call Canvas1.Clear. In when Button6.Click → call Canvas1.SaveAs fileName "gin-drawing.png"; set Label1.Text to "Saved as gin-drawing.png!". In when Canvas1.SavedAs fileName (if available) → set Label1.Text to join "Saved: " + fileName`. Note: the saved file goes to the phone's storage; it can be viewed in the phone's gallery/files app.

3) Test: Draw a resistor symbol (zigzag) in red, a circle in blue, clear it, then draw a simple

circuit and save it. 90-minute timing: 0–10 plan/sketch — sketch a resistor zigzag and a simple circuit on paper; 10–20 demo — Rica draws one line and changes colour mid-drawing; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test each colour, tap-dot, clear and save; 80–90 share — draw a circuit diagram and save it. Test checklist: Dragging draws a line in the chosen colour; tapping draws a dot; changing colour changes the next line only; Clear empties the canvas; Save reports the file name. Common bug: all lines draw in black whatever colour is picked — fix: check Canvas1.PaintColor is set to get global penColour inside the Dragged event before DrawLine, not only in the colour buttons. Success check: Gin can draw in four colours, clear the canvas, and save a drawing to the phone. Homework: Draw a full simple circuit (battery, resistor, LED) and save it, then show it to Rica next week.

Session 51Location sensor — show latitude / longitude (exploration, privacy note)Wed 3 Nov 2027
Wed 3 Nov 2027 | Phase 4 — Sensors & Media

Date: Wed 3 Nov 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can use the LocationSensor to show his phone's latitude and longitude, and can explain why location data must stay private and never be shared. Components: Screen1 — Label1, Text "Where Am I?", FontSize 20, Bold true; Label2, Text "Latitude: —", FontSize 18; Label3, Text "Longitude: —", FontSize 18; Label4, Text "Accuracy: — m", FontSize 16; Button1, Text "Get my location", FontSize 18; Label5, Text "⚠ Private: never share your location with strangers or post it online.", FontSize 14; LocationSensor1 (non-visible), Enabled true, TimeInterval 5000, DistanceInterval 5. Step-by-step build:

1) Designer setup: Add the title label, the latitude/longitude/accuracy labels, the Get location

button and the privacy warning label (keep it visible on screen at all times). Add LocationSensor1.

2) Blocks setup: In when Button1.Click → `set Label2.Text to "Waiting for GPS…"; set

Label3.Text to ""; call LocationSensor1.Refresh — actually the sensor updates on its own; use: set Label2.Text to join "Latitude: " + LocationSensor1.Latitude and the same for Longitude and LocationSensor1.Accuracy. Better: in when LocationSensor1.LocationChanged latitude longitude altitude → set Label2.Text to join "Latitude: " + latitude, set Label3.Text to join "Longitude: " + longitude, set Label4.Text to join "Accuracy: ±" + round LocationSensor1.Accuracy + " m". In when Button1.Click → set Label2.Text to "Waiting for GPS…" and rely on the LocationChanged event to fill the values in. Also add a check: if LocationSensor1.AvailableProviders contains "gps" then set Label5.Text to "GPS is available."` — keep the privacy warning as the main Label5 text and do not overwrite it; put the GPS note in a separate small label if wanted.

3) Test: Tap Get my location outdoors or near a window, wait a few seconds, and check the numbers

appear. Compare with a maps app if Rica agrees — but do not type or share the numbers anywhere. 90-minute timing: 0–10 plan/sketch — talk through the privacy rule first: location stays on his own phone, never sent or posted; 10–20 demo — Rica shows her own phone's latitude/longitude appearing; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test near a window, check accuracy improves outdoors; 80–90 share — show the numbers on his own phone only, and repeat the privacy rule in his own words. Test checklist: Tapping the button eventually shows latitude and longitude; accuracy is shown in metres; the privacy warning is visible on screen; nothing is sent anywhere (no Web or sharing blocks in this app). Common bug: latitude stays 0 or blank — fix: check location permission is allowed for the Companion app, go near a window or outside (GPS does not work well indoors), and wait — the first fix can take 30–60 seconds. Note: this session is exploration — GPS accuracy varies, the emulator shows a fixed fake location, and the numbers must never leave his phone. Success check: Gin can show his latitude and longitude on his own phone and explain in his own words why he must not share them. Homework: Write down (on paper, not in the app) one place where showing location is useful (e.g. maps) and one place where it is dangerous.

Session 52Pedometer — step counter with accelerometerWed 10 Nov 2027
Wed 10 Nov 2027 | Phase 4 — Sensors & Media

Date: Wed 10 Nov 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build a step counter that counts steps from the phone's movement and shows the total, with start/stop and reset. Components: Screen1 — Label1, Text "Step Counter", FontSize 20, Bold true; Label2, Text "Steps: 0", FontSize 28, Bold true; Button1, Text "Start counting", FontSize 18; Button2, Text "Stop", FontSize 18; Button3, Text "Reset", FontSize 18; Label3, Text "Goal: 100 steps", FontSize 16; Pedometer1 (non-visible); Clock1 (non-visible), TimerInterval 1000, TimerEnabled false. Step-by-step build:

1) Designer setup: Add the title label, the big steps label, Start/Stop/Reset buttons and the goal

label. Add Pedometer1 and Clock1.

2) Blocks setup: Make global variables steps = 0 and counting = false. In when Button1.Click

→ set global counting to true; call Pedometer1.Start; set Label3.Text to "Counting… walk around!". In when Pedometer1.StepCountChanged steps — the Pedometer component fires events as steps are detected; use: when Pedometer1.SimpleStepChanged simpleSteps → set global steps to get global steps + simpleSteps; set Label2.Text to join "Steps: " + get global steps; if get global steps ≥ 100 then set Label3.Text to "Goal reached! 🎉 100 steps!". (App Inventor's Pedometer has SimpleStepChanged and WalkStepChanged events — use SimpleStepChanged.) In when Button2.Click → call Pedometer1.Stop; set global counting to false; set Label3.Text to "Stopped.". In when Button3.Click → set global steps to 0; set Label2.Text to "Steps: 0"; set Label3.Text to "Goal: 100 steps". Note: the Pedometer needs the phone to be carried while walking — it will not count steps if the phone sits on the desk.

3) Test: Start counting, walk around the room for one minute holding the phone, and check the

number goes up. Stop, reset, and check it returns to 0. 90-minute timing: 0–10 plan/sketch — decide the goal (100 steps) and where he will walk; 10–20 demo — Rica walks 10 steps with the phone and shows the count; 20–65 build — Designer + Blocks as above; 65–80 test & fix — walk test, stop/reset test; 80–90 share — a 100-step race with Ray and Run. Test checklist: Steps increase while walking with the phone; Stop freezes the count; Reset returns to 0; reaching 100 shows the goal message. Common bug: the counter stays at 0 while walking — fix: check Pedometer1.Start was called (Start button tapped), the phone is being carried (not on the desk), and test on a real phone — the emulator has no pedometer. Some phones count slowly or need a few steps before the first event fires. Success check: Gin can count real steps by walking with the phone and reset the counter. Homework: Count his steps on the walk home (or around the house) and write down the total to compare next week.

Session 53Compass — show heading, rotate an imageWed 17 Nov 2027
Wed 17 Nov 2027 | Phase 4 — Sensors & Media

Date: Wed 17 Nov 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can build a compass that shows the heading in degrees and the direction name (N, NE, E…) and rotates a needle image to match. Components: Screen1 — Label1, Text "Compass", FontSize 20, Bold true; Label2, Text "Heading: 0°", FontSize 24, Bold true; Label3, Text "Direction: North", FontSize 18; ImageSprite1 — use Canvas1, Width 300, Height 300, with ImageSprite1 (a needle/arrow image, Width 60, Height 200, or draw the needle with canvas lines); Button1, Text "Reset", FontSize 16; OrientationSensor1 (non-visible), Enabled true. Step-by-step build:

1) Designer setup: Add Canvas1 (300 × 300) and an ImageSprite1 needle on it — use a simple arrow

image (upload one, or draw a triangle arrow). Add the heading and direction labels and the Reset button. Add OrientationSensor1.

2) Blocks setup: Make a global variable heading = 0. In `when

OrientationSensor1.OrientationChanged azimuth pitch roll → set global heading to round azimuth, set Label2.Text to join "Heading: " + get global heading + "°", then set the direction name: if get global heading < 22.5 or get global heading ≥ 337.5 then set Label3.Text to "Direction: North" else if get global heading < 67.5 then set Label3.Text to "Direction: North-East" else if get global heading < 112.5 then set Label3.Text to "Direction: East" else if get global heading < 157.5 then set Label3.Text to "Direction: South-East" else if get global heading < 202.5 then set Label3.Text to "Direction: South" else if get global heading < 247.5 then set Label3.Text to "Direction: South-West" else if get global heading < 292.5 then set Label3.Text to "Direction: West" else set Label3.Text to "Direction: North-West". Then rotate the needle: set ImageSprite1.Heading to get global heading — a sprite's Heading rotates it to point that way. In when Button1.Click → set Label2.Text to "Heading: 0°"; set Label3.Text to "Direction: North"`.

3) Test: Hold the phone flat and slowly turn around in a circle — the heading number should rise

from 0 to 360 and the needle should spin with it. Face a known direction and check the name matches. 90-minute timing: 0–10 plan/sketch — sketch the compass circle and the 8 direction names with their degree ranges; 10–20 demo — Rica turns slowly and shows the heading changing; 20–65 build — Designer + Blocks as above; 65–80 test & fix — full 360° turn test, check each direction name; 80–90 share — point the phone at the door and read out the direction. Test checklist: Heading updates live from 0–360°; the direction name matches the heading range; the needle rotates with the phone; the compass works best with the phone held flat. Common bug: heading jumps around or the needle points the wrong way — fix: hold the phone flat (tilting it changes the reading), and check the sprite Heading is set from azimuth, not pitch or roll; some phones need a figure-of-eight wave to calibrate the compass first. Success check: Gin can turn in a circle and read the correct heading and direction name at each point. Homework: Use the compass to find which direction his classroom window faces and write it down.

Session 54Proximity / light sensor — change screen when covered / dark (device-dependent)Wed 24 Nov 2027
Wed 24 Nov 2027 | Phase 4 — Sensors & Media

Date: Wed 24 Nov 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can explain that App Inventor has no built-in proximity or light sensor component, and build a working "cover the phone" demo using the blocks that do exist, with a clear note on what is device-dependent. Components: Screen1 — Label1, Text "Cover Sensor Demo", FontSize 20, Bold true; Label2, Text "Screen: Bright ☀", FontSize 24, Bold true; Button1, Text "Simulate: Cover phone", FontSize 18; Button2, Text "Simulate: Uncover", FontSize 18; Label3, Text "Note: App Inventor has no built-in proximity or light sensor. This demo uses buttons to show the logic.", FontSize 14; Clock1 (non-visible), TimerInterval 2000, TimerEnabled false. Step-by-step build:

1) Designer setup: Add the title label, the big status label, the two simulate buttons and the

honest note label. Say it plainly at the start of the session: MIT App Inventor has no ProximitySensor and no LightSensor component in its standard palette, so a real cover-the-phone trigger cannot be built in blocks alone. What Gin builds today is the exact logic a real sensor app would use, driven by buttons, so the design is ready if a sensor extension is ever added.

2) Blocks setup: Make global variable covered = false. Make a procedure setCovered value: `set

global covered to value; if get global covered then set Screen1.BackgroundColor to black; set Label1.TextColor to white; set Label2.TextColor to white; set Label2.Text to "Screen: Dark 🌙 — phone covered!" else set Screen1.BackgroundColor to white; set Label1.TextColor to black; set Label2.TextColor to black; set Label2.Text to "Screen: Bright ☀". In when Button1.Click → call setCovered true. In when Button2.Click → call setCovered false. Extension test (optional, only if Rica finds a trusted sensor extension before the session): replace the two buttons with the extension's event block calling setCovered true/false` — do not install an unknown extension on the day without checking it first.

3) Test: Tap "Cover phone" — the screen must go dark with the moon message. Tap "Uncover" — it

must return to bright. Test the real phone's own behaviour too: cover the top of the phone during a call and notice the screen turns off by itself — that is the phone's own proximity sensor, not the app. 90-minute timing: 0–10 plan/sketch — discuss what a proximity sensor does (phone calls) and why App Inventor lacks one; 10–20 demo — Rica shows the phone screen turning off during a call, then the button demo; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test both buttons and the dark/light switch; 80–90 share — explain to Ray and Run why this session is a simulation, not a real sensor reading. Test checklist: Cover button turns the screen dark with the right message; Uncover restores bright; the note label explains the limitation honestly; Gin can say in his own words why the app cannot sense covering by itself. Common bug: text becomes invisible on the dark screen — fix: check setCovered changes the TextColor of every label (Label1, Label2, Label3) to white when dark and black when bright. Success check: Gin can demo the cover/uncover logic and explain plainly that App Inventor has no built-in proximity or light sensor. Homework: Find one app on his phone that uses a real sensor (e.g. auto-brightness) and write down what it does.

Session 55Media app — gallery + sound + video in one appWed 1 Dec 2027
Wed 1 Dec 2027 | Phase 4 — Sensors & Media

Date: Wed 1 Dec 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can combine his camera gallery, sound recorder and video player into one media app with three screens (or tabs) and navigation between them. Components: Screen1 ("Home") — Label1, Text "My Media App", FontSize 20, Bold true; Button1, Text "📷 Photos", FontSize 18; Button2, Text "🔊 Sounds", FontSize 18; Button3, Text "🎬 Videos", FontSize 18. Screen2 ("Photos") — reuse Session 45 blocks: ListView1, Image1, Button "Take photo", Camera1, TinyDB1. Screen3 ("Sounds") — reuse Session 46 blocks: Record/Stop/Play buttons, ListView1, SoundRecorder1, Player1, TinyDB1. Screen4 ("Videos") — reuse Session 49 blocks: VideoPlayer1, Play/Pause/Stop buttons, Clock1. Each of Screens 2–4 has a Button "⌂ Home" that closes the screen. Step-by-step build:

1) Designer setup: Build the Home screen with three big navigation buttons. Copy the Designer

layouts from Sessions 45, 46 and 49 into Screens 2, 3 and 4 (App Inventor cannot copy a whole screen, so rebuild each one — this is good revision). Add a Home button on each of the three screens.

2) Blocks setup: On Home: when Button1.Click → open another screen "Photos", Button2 →

"Sounds", Button3 → "Videos". On each other screen: when HomeButton.Click → close screen. Then paste in the Blocks from the matching session: Photos screen gets the Session 45 Camera + TinyDB list blocks (tags "photos"/"paths"); Sounds screen gets the Session 46 SoundRecorder + Player blocks (tags "names"/"paths" — note the two screens use different TinyDB namespaces, "PhotoGallery" and "Recordings", so their tags cannot clash); Videos screen gets the Session 49 VideoPlayer + Clock blocks. Keep each screen's TinyDB namespace exactly as it was in its original session.

3) Test: From Home, open Photos, take a photo, go Home, open Sounds, record and play a clip, go

Home, open Videos and play a clip. Check every screen returns Home cleanly. 90-minute timing: 0–10 plan/sketch — sketch the Home screen and the three sections; 10–20 demo — Rica opens each of the three old apps and shows what will be combined; 20–65 build — rebuild the three screens and the navigation; 65–80 test & fix — full round trip through all three sections and back Home; 80–90 share — demo the whole media app start to finish. Test checklist: All three Home buttons open the right screen; each section still works as it did alone (photo saves, sound plays, video plays); Home buttons return to Home; no screen crashes on opening. Common bug: a section that worked alone now shows nothing — fix: check its TinyDB namespace and tags were copied exactly, and that its components (Camera1, SoundRecorder1, VideoPlayer1) were re-added on the new screen, since components do not carry over between screens. Success check: Gin can open Photos, Sounds and Videos from one Home screen and use each one. Homework: Add a fourth Home button "Draw" that opens a screen with the Session 50 drawing canvas.

Session 56Sensors showcase — demo best sensor app, fix sensor bugsWed 8 Dec 2027
Wed 8 Dec 2027 | Phase 4 — Sensors & Media

Date: Wed 8 Dec 2027 | Phase: Phase 4 — Sensors & Media Learning objective: Gin can demo his best sensor and media apps, list the sensor bugs found across Phase 4, and fix them. Components: No new app — reuse the Session 41–55 apps on the phone. Paper checklist with the 8 sensor/media apps: Tilt Maze, Orientation Car, Sound Trigger, Camera, Photo Gallery, Sound Recorder, Text-to-Speech, Speech Recognizer, Video Player, Drawing, Location, Pedometer, Compass, Media App. Step-by-step build:

1) Designer setup: No new Designer work — open each Phase 4 project and list it on the paper

checklist with two columns: "Works on the phone?" and "Works in the emulator?".

2) Blocks setup: For each app, run the same test: open with Companion on the real phone, use the

sensor or media feature, then try the same thing in the emulator and note the difference. The expected pattern: accelerometer, orientation, camera, recorder, pedometer, compass and location need the real phone; text-to-speech and drawing mostly work in both. For every bug, write it down with the fix: e.g. "Tilt maze ball too fast → changed × 5 to × 3", "Speech recognizer needs internet → test with Wi-Fi on", "Photo gallery wrong photo → fixed SelectionIndex". Fix each bug in Blocks, then retest on the phone.

3) Test: Finish with a demo round — Gin picks his best sensor app and his best media app and

presents both to Ray, Run and Rica, including one bug he fixed and how. 90-minute timing: 0–10 plan/sketch — write the checklist of Phase 4 apps; 10–20 demo — Rica demos one sensor app on the phone and the same app failing in the emulator; 20–65 build — test every app, fix bugs; 65–80 test & fix — retest every fixed app on the phone; 80–90 share — demo round: best sensor app + best media app + one bug fix explained. Test checklist: Every app is tested on the real phone; every bug found has a written fix and a passing retest; Gin can say which sensors need a real phone and why. Common bug: testing only in the emulator and concluding a sensor is broken — fix: always retest sensors on the real phone with Companion before changing any Blocks. Success check: Gin can demo his best sensor and media apps and explain one bug he fixed in each. Homework: Pick his single best Phase 4 app and write down two improvements for Phase 5.

Session 57Bluetooth basics — scan, pair, connect (exploration)Wed 15 Dec 2027
Wed 15 Dec 2027 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 15 Dec 2027 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can scan for nearby Bluetooth devices, show them in a list, and connect to one — and can explain that Bluetooth needs a second device and permission. Components: Screen1 — Label1, Text "Bluetooth Basics", FontSize 20, Bold true; Button1, Text "Scan for devices", FontSize 18; ListPicker1, Text "Devices found", FontSize 16; Label2, Text "Status: not connected", FontSize 16; Button2, Text "Disconnect", FontSize 16; BluetoothClient1 (non-visible); BluetoothServer1 (non-visible, only if testing two phones both running the app). Step-by-step build:

1) Designer setup: Add the title label, the Scan button, ListPicker1, the status label and the

Disconnect button. Add BluetoothClient1. What is needed: a second Bluetooth device nearby — another phone, a tablet, or a Bluetooth speaker/headphones just to appear in the scan. If no second device is available, use the fallback: scan anyway and record what appears (the classroom may have devices), or practise with the emulator's fake list — do not invent a device that is not there.

2) Blocks setup: In when Button1.Click → `set Label2.Text to "Scanning…"; set

ListPicker1.Elements to BluetoothClient1.AddressesAndNames. In when ListPicker1.AfterPicking → set Label2.Text to join "Picked: " + ListPicker1.Selection; call BluetoothClient1.Connect address select list item list BluetoothClient1.Addresses index ListView1.SelectionIndex — in blocks: call BluetoothClient1.Connect address call BluetoothClient1.AddressesAndNames is not right; the correct pattern is: set global pickedAddress to select list item list BluetoothClient1.Addresses index ListPicker1.SelectionIndex then call BluetoothClient1.Connect address get global pickedAddress. Add a global variable pickedAddress = "". In when BluetoothClient1.Connected — App Inventor fires no Connected event on the client; instead check after the call: if BluetoothClient1.IsConnected then set Label2.Text to "Connected!" else set Label2.Text to "Could not connect — is the other device paired?". Put that check right after the Connect call and also on a "Check connection" tap. In when Button2.Click → call BluetoothClient1.Disconnect; set Label2.Text to "Status: not connected"`.

3) Test: Turn on Bluetooth on both phones, make the second phone visible/discoverable, tap Scan,

pick the second phone, and check the status shows Connected. If pairing is asked for, accept it on both phones — pairing needs the other phone's owner (Rica) to approve it. 90-minute timing: 0–10 plan/sketch — list what Bluetooth is used for and what second device is available today; 10–20 demo — Rica scans and shows the real device list; 20–65 build — Designer + Blocks as above; 65–80 test & fix — scan, pick, connect, disconnect, then scan again; 80–90 share — show the connected status to Ray and Run and explain pairing in his own words. Test checklist: Scan shows real nearby device names; picking one attempts a connection; the status label says Connected or explains why not; Disconnect returns to "not connected". Common bug: the list is empty — fix: check Bluetooth is on, the other device is discoverable/visible, and location permission is allowed (Android needs it for Bluetooth scanning); do not invent a device — if none appears, note it and use the fallback of scanning again near a different device. Success check: Gin can scan, pick a real device, and connect to it — or explain exactly why no device was found. Homework: Write down three devices at home that use Bluetooth and what each one connects to.

Session 58Bluetooth chat — send a message to another phoneWed 22 Dec 2027
Wed 22 Dec 2027 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 22 Dec 2027 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can build a Bluetooth chat app that sends a typed message to a second phone and shows messages received from it. Components: Screen1 — Label1, Text "Bluetooth Chat", FontSize 20, Bold true; Button1, Text "Connect", FontSize 18; TextBox1, Hint "Type a message", FontSize 16; Button2, Text "Send", FontSize 18; Label2, Text "Chat:", FontSize 16; Label3, Text "", FontSize 16; BluetoothClient1 (non-visible); BluetoothServer1 (non-visible); Clock1 (non-visible), TimerInterval 500, TimerEnabled false. Step-by-step build:

1) Designer setup: Add the title label, Connect button, message TextBox, Send button and two labels

(one "Chat:" header, one for the chat history). Add BluetoothClient1, BluetoothServer1 and Clock1. What is needed: a second phone with the same chat app installed (or the Companion app running the same project) and both phones paired — Rica's phone is the second phone. If no second phone is available, use the fallback: test sending a message to himself by running the app on his phone and the Companion on Rica's phone, or practise the send/receive logic with a pretend reply in a label — do not claim a message was received when it was not.

2) Blocks setup: Make global variable chatHistory = "". First, the server side (so the other

phone can connect to this one): in when Screen1.Initialize → call BluetoothServer1.AcceptConnection "chat". In when Button1.Click → use the Session 57 pattern: set ListPicker — simpler for this session: add a ListPicker1 "Pick a device" and in when ListPicker1.AfterPicking → call BluetoothClient1.Connect address select list item list BluetoothClient1.Addresses index ListPicker1.SelectionIndex. In when Button2.Click → if TextBox1.Text ≠ "" and BluetoothClient1.IsConnected then call BluetoothClient1.SendText text TextBox1.Text; set global chatHistory to join get global chatHistory + "\nMe: " + TextBox1.Text; set Label3.Text to get global chatHistory; set TextBox1.Text to "" else set Label3.Text to "Connect first, then type a message!". For receiving: when Clock1.Timer → if BluetoothClient1.IsConnected and BluetoothClient1.BytesAvailableToReceive > 0 then set global chatHistory to join get global chatHistory + "\nFriend: " + BluetoothClient1.ReceiveText; set Label3.Text to get global chatHistory. Enable the Clock in Screen1.Initialize (set Clock1.TimerEnabled to true) so it keeps checking for incoming messages. Also handle the server side: when BluetoothServer1.ConnectionAccepted → set Label2.Text to "Chat: connected!".

3) Test: Pair the two phones, connect, type "Hello from Gin" on his phone, and check it appears on

Rica's phone — then reply from Rica's phone and check it appears on his. 90-minute timing: 0–10 plan/sketch — write 3 test messages and who sends each; 10–20 demo — Rica shows the two phones side by side and one message crossing over; 20–65 build — Designer + Blocks as above; 65–80 test & fix — send both ways, test the not-connected warning; 80–90 share — a live two-phone chat with Ray or Run watching. Test checklist: Messages sent from Gin's phone appear on the second phone; replies appear on Gin's phone; Send with no connection shows the warning; the chat history keeps both sides in order. Common bug: messages send but nothing is received — fix: check the Clock is enabled (it polls for incoming text), that BytesAvailableToReceive > 0 is checked before ReceiveText, and that both phones are actually connected (check IsConnected on both). Success check: Gin can send a message from his phone and see a reply from the second phone in the same chat. Homework: Add the sender's name to each line ("Gin: …") and a "Clear chat" button.

Session 59Bluetooth remote — buttons send commands to a second deviceWed 29 Dec 2027
Wed 29 Dec 2027 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 29 Dec 2027 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can build a Bluetooth remote where buttons on his phone send short commands ("LED_ON", "LED_OFF", "BEEP") to a second device, which acts on them. Components: Screen1 (remote) — Label1, Text "Bluetooth Remote", FontSize 20, Bold true; Button1, Text "💡 LED ON", FontSize 18; Button2, Text "LED OFF", FontSize 18; Button3, Text "🔔 BEEP", FontSize 18; Button4, Text "Connect", FontSize 16; Label2, Text "Status: not connected", FontSize 16; BluetoothClient1 (non-visible). Screen 2 (receiver, same app on the second phone) — Label1, Text "Receiver", FontSize 20, Bold true; Label2, Text "Waiting for a command…", FontSize 18; Button1, Text "LED (tap = the remote's light)", FontSize 18, BackgroundColor gray; BluetoothServer1 (non-visible); Clock1, TimerInterval 500, TimerEnabled true. Step-by-step build:

1) Designer setup: Build the remote screen with the three command buttons, Connect and the status

label. On the second phone the same project shows a receiver screen — in practice build two screens in one project ("Remote" and "Receiver") and open the right one on each phone, or build the receiver as a second small project. What is needed: a second phone running the receiver (Rica's phone). If no second phone is available, use the fallback: the remote sends commands to a label on the same phone that pretends to be the receiver — do not claim a second device acted when it did not.

2) Blocks setup (remote): In when Button4.Click → connect as in Session 58 (ListPicker +

BluetoothClient1.Connect). In when Button1.Click → if BluetoothClient1.IsConnected then call BluetoothClient1.SendText text "LED_ON"; set Label2.Text to "Sent: LED_ON" else set Label2.Text to "Connect first!". Button2 sends "LED_OFF", Button3 sends "BEEP". Blocks setup (receiver): in when Screen Initialize → call BluetoothServer1.AcceptConnection "remote". In when Clock1.Timer → if BluetoothServer1.IsConnected and BluetoothServer1.BytesAvailableToReceive > 0 then set global command to BluetoothServer1.ReceiveText; if get global command = "LED_ON" then set Button1.BackgroundColor to yellow; set Label2.Text to "LED is ON" else if get global command = "LED_OFF" then set Button1.BackgroundColor to gray; set Label2.Text to "LED is OFF" else if get global command = "BEEP" then set Label2.Text to "BEEP! 🔔".

3) Test: Connect the two phones, tap LED ON on the remote, and check the receiver phone's button

turns yellow. Tap LED OFF and BEEP and check each one. 90-minute timing: 0–10 plan/sketch — list the 3 commands and what each should do on the receiver; 10–20 demo — Rica shows one command crossing between the two phones; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test all three commands both ways, test the not-connected warning; 80–90 share — let Ray or Run press the remote while Gin watches the receiver. Test checklist: Each remote button sends its exact command text; the receiver acts correctly on all three; sending with no connection shows the warning; the receiver's status label always matches the last command. Common bug: the receiver never reacts — fix: check the receiver's Clock is enabled and polling, that the command text matches exactly ("LED_ON" with underscore and capitals — "led_on" will not match), and that the server accepted the connection before the remote sent anything. Success check: Gin can press a button on his phone and make something happen on the second phone. Homework: Add a fourth command "FLASH" that turns the receiver LED yellow, waits 1 second, then turns it off again (use a Clock timer on the receiver).

Session 60Bluetooth + micro:bit — send a message to a micro:bit, show reply (exploration, if device available)Wed 5 Jan 2028
Wed 5 Jan 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 5 Jan 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can send a short message from his phone to a micro:bit over Bluetooth and show the micro:bit's reply — and can explain what to do when no micro:bit is available. Components: Screen1 — Label1, Text "Phone ↔ micro:bit", FontSize 20, Bold true; Button1, Text "Connect to micro:bit", FontSize 18; TextBox1, Hint "Message, e.g. HELLO", FontSize 16; Button2, Text "Send", FontSize 18; Label2, Text "micro:bit says: —", FontSize 18; Label3, Text "", FontSize 16; BluetoothClient1 (non-visible); Clock1, TimerInterval 500, TimerEnabled true. Step-by-step build:

1) Designer setup: Add the title label, Connect button, message TextBox, Send button and the two

labels. Add BluetoothClient1 and Clock1. What is needed: a real micro:bit (v1 or v2) with a Bluetooth program on it that receives text and replies — the micro:bit must be programmed separately (in MakeCode, blocks) to show the message on its LEDs and send a reply back. If no micro:bit is available on the day, use the fallback: build the whole phone side exactly as below and test it against Rica's phone running a tiny receiver (Session 58's chat app) standing in for the micro:bit — do not claim the micro:bit replied when it was a phone. Say plainly in the session: this is exploration, and it only works end-to-end when a programmed micro:bit is in the room.

2) Blocks setup: Make global variable replyText = "". In when Button1.Click → scan and

connect as in Session 57, picking the micro:bit's Bluetooth name (it appears as something like "BBC micro:bit [xxxxx]" — the exact name is on the back of the device). In when Button2.Click → if BluetoothClient1.IsConnected and TextBox1.Text ≠ "" then call BluetoothClient1.SendText text TextBox1.Text; set Label3.Text to join "Sent: " + TextBox1.Text; set TextBox1.Text to "" else set Label3.Text to "Connect to the micro:bit first!". In when Clock1.Timer → if BluetoothClient1.IsConnected and BluetoothClient1.BytesAvailableToReceive > 0 then set global replyText to BluetoothClient1.ReceiveText; set Label2.Text to join "micro:bit says: " + get global replyText. Note: the micro:bit's Bluetooth service speaks in short messages; long messages may be cut off, so keep messages under about 20 characters.

3) Test: Connect, send "HELLO", watch the micro:bit's LEDs show the message, and check its reply

appears in Label2. If the micro:bit is absent, test the same flow against the stand-in phone and write down what still needs the real device. 90-minute timing: 0–10 plan/sketch — check whether a micro:bit is in the room and what program is on it; 10–20 demo — Rica shows the micro:bit's Bluetooth name in a scan; 20–65 build — Designer + Blocks as above; 65–80 test & fix — send a message, watch for the reply, test the stand-in fallback if needed; 80–90 share — show the message on the micro:bit LEDs and the reply on the phone. Test checklist: The micro:bit appears in the scan (or the fallback is used and named as such); sending shows the message on the micro:bit; the reply appears in Label2; sending with no connection shows the warning. Common bug: the phone connects but the micro:bit shows nothing — fix: check the micro:bit actually has a Bluetooth receive program on it (a blank micro:bit does nothing), that the message is short, and that the micro:bit is paired; the phone side cannot fix a micro:bit with no program. Success check: Gin can send a message to the micro:bit and show its reply — or explain exactly which piece was missing and how the fallback test worked. Homework: In MakeCode (blocks), write down the 3 blocks the micro:bit needs: on Bluetooth receive → show string → send a reply.

Session 61Web basics — Web component, get a web page titleWed 12 Jan 2028
Wed 12 Jan 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 12 Jan 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can use the Web component to fetch a web page and show its title on screen. Components: Screen1 — Label1, Text "Web Basics", FontSize 20, Bold true; TextBox1, Hint "Web address, e.g. https://example.com", Text "https://example.com", FontSize 14; Button1, Text "Get page title", FontSize 18; Label2, Text "Title: —", FontSize 18; Label3, Text "", FontSize 16; Web1 (non-visible). Step-by-step build:

1) Designer setup: Add the title label, the address TextBox (pre-filled with https://example.com),

the Get title button and the two labels. Add Web1 from Connectivity. What is needed: internet (Wi-Fi or mobile data) — without it the request fails, and the app must say so. No API key is needed for this session.

2) Blocks setup: In when Button1.Click → `set Label3.Text to "Loading…"; call Web1.Get url

TextBox1.Text — set Web1.Url first: set Web1.Url to TextBox1.Text; call Web1.Get. In when Web1.GotText url responseCode responseType responseContent → if responseCode = 200 then set Label2.Text to join "Title: " + call extractTitle responseContent else set Label2.Text to join "Could not load the page (code " + responseCode + ")"; set Label3.Text to "". The title extraction: App Inventor has no built-in HTML parser, so extract it with text blocks — make a procedure extractTitle html: set local start to call text segment... — use the contains and segment blocks: find the position of "<title>" with the text find pattern, then segment from after "<title>" to before "</title>". In blocks: set local startPos to find "<title>" in html (use the text block with find), set local endPos to find "</title>" in html, if startPos > 0 and endPos > startPos then return segment html start startPos + 7 length endPos - (startPos + 7) else return "(no title found)"`. Keep the procedure simple and test it with example.com, whose title is "Example Domain".

3) Test: Tap Get page title with example.com and check "Title: Example Domain" appears. Then try a

second safe address (e.g. https://www.wikipedia.org) and check its title appears. 90-minute timing: 0–10 plan/sketch — discuss what a web request is: ask for a page, get text back; 10–20 demo — Rica fetches example.com and shows the title; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test both addresses, test with Wi-Fi off to see the failure message; 80–90 share — fetch the title of a page Gin chooses and read it out. Test checklist: example.com returns "Example Domain"; a second page returns its real title; turning Wi-Fi off shows a clear failure message instead of crashing; the address box accepts a typed address. Common bug: the title shows as "(no title found)" or blank — fix: check the find positions (the "<title>" text must match exactly, lowercase) and that GotText uses responseContent, not responseType; some pages have no title tag or block the request, so test with example.com first. Success check: Gin can fetch a page and display its title, and explain what happens with no internet. Homework: Fetch the titles of 3 safe pages and write down each title next to its address.

Session 62Weather app — call a public weather API, show temperature (exploration)Wed 19 Jan 2028
Wed 19 Jan 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 19 Jan 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can call a public weather API with the Web component and show the temperature for a city — and can explain that a real API needs a key and that results are not guaranteed. Components: Screen1 — Label1, Text "Weather App", FontSize 20, Bold true; TextBox1, Hint "City, e.g. Bangkok", Text "Bangkok", FontSize 16; Button1, Text "Get weather", FontSize 18; Label2, Text "Temperature: —", FontSize 20, Bold true; Label3, Text "Weather: —", FontSize 16; Label4, Text "", FontSize 14; Web1 (non-visible). Step-by-step build:

1) Designer setup: Add the title label, the city TextBox (pre-filled "Bangkok"), the Get weather

button, the temperature and weather labels and a status label. Add Web1. What is needed: internet, plus a weather API endpoint and key. Do not invent a key. The honest plan for the session: use the free Open-Meteo API, which needs no key — https://api.open-meteo.com/v1/forecast?latitude=13.75&longitude=100.5&current=temperature_2m,weathe r_code for Bangkok (latitude 13.75, longitude 100.5). If Open-Meteo is unreachable or its format has changed by the session date, use the fallback: a built-in sample reply stored in a variable, e.g. {"temperature": 32, "weather": "sunny (sample data)"}, and label it clearly as sample data. If Rica prefers a key-based service (e.g. OpenWeatherMap), the key must be obtained by an adult before the session and pasted into the URL — Gin must never be asked to sign up for or share a key.

2) Blocks setup: Make global variable useSampleData = false. In when Button1.Click → `set

Label4.Text to "Loading…"; set Web1.Url to join "https://api.open-meteo.com/v1/forecast?latitude=13.75&longitude=100.5&current=temperature_2m,weathe r_code"; call Web1.Get. (For other cities, look up the latitude/longitude first and change the numbers — do not guess them; Bangkok's are given above.) In when Web1.GotText url responseCode responseType responseContent → if responseCode = 200 then call showWeather responseContent else set Label4.Text to join "Could not load weather (code " + responseCode + ") — showing sample data"; call showWeatherSample. Procedure showWeather jsonText: the reply is JSON text; App Inventor has no built-in JSON parser in the standard Web component, so extract the temperature with text blocks: find "temperature_2m": with find, then segment the number after it up to the next comma, and set Label2.Text to join "Temperature: " + that number + " °C". Find "weather_code": the same way and map the code with an if chain: 0 → "Clear sky", 1–3 → "Partly cloudy", 45/48 → "Foggy", 51–67 → "Rain", 71–77 → "Snow", 80–82 → "Rain showers", 95 → "Thunderstorm", else "Weather code " + the code. Set Label3 accordingly and Label4 to "Live data from Open-Meteo". Procedure showWeatherSample: set Label2.Text to "Temperature: 32 °C (sample)"; set Label3.Text to "Weather: sunny (sample)"; set Label4.Text to "Sample data — the API did not reply"`.

3) Test: Tap Get weather and check a temperature appears with "Live data" or an honest "sample

data" label. Turn Wi-Fi off and check the sample fallback appears instead of a crash. 90-minute timing: 0–10 plan/sketch — discuss what an API is and why a key is sometimes needed; 10–20 demo — Rica shows a real API reply (raw text) and points out the temperature number inside it; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test live, test offline fallback, test a second city if its coordinates are known; 80–90 share — show Bangkok's temperature and explain where the number came from. Test checklist: A live temperature appears when online; the weather description matches the code; offline shows sample data clearly labelled as sample; no API key is typed or invented anywhere. Common bug: the temperature label shows a wrong number or blank — fix: check the find text matches the API reply exactly ("temperature_2m": with quotes and colon) and re-read the raw reply in a label first to see its real format before parsing it. Success check: Gin can show Bangkok's temperature from a public API and say honestly whether the number is live or sample data. Homework: Look up the latitude and longitude of one other city (with Rica) and fetch its weather too.

Session 63Currency / unit converter via Web — fetch a rate, convert (exploration)Wed 26 Jan 2028
Wed 26 Jan 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 26 Jan 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can fetch a currency exchange rate from a public API and use it to convert an amount (e.g. THB to USD), with sample data as a fallback. Components: Screen1 — Label1, Text "Currency Converter", FontSize 20, Bold true; TextBox1, Hint "Amount in THB", NumbersOnly true, FontSize 16; Button1, Text "Convert THB → USD", FontSize 18; Label2, Text "Rate: —", FontSize 16; Label3, Text "Result: —", FontSize 20, Bold true; Label4, Text "", FontSize 14; Web1 (non-visible). Step-by-step build:

1) Designer setup: Add the title label, the amount TextBox, the Convert button, the rate/result

labels and a status label. Add Web1. What is needed: internet and a public exchange-rate API. Do not invent a key. The honest plan: use the free Frankfurter API, which needs no key — https://api.frankfurter.app/latest?from=THB&to=USD. If it is unreachable or its format has changed by the session date, use the fallback: a built-in sample rate stored in a variable (e.g. 0.028, labelled "sample rate — not live") and do the conversion with that. Never hard-code a rate and present it as live.

2) Blocks setup: Make global variable rate = 0. In when Button1.Click → `if TextBox1.Text =

"" then set Label3.Text to "Enter an amount first!" else set Label4.Text to "Loading rate…"; set Web1.Url to "https://api.frankfurter.app/latest?from=THB&to=USD"; call Web1.Get. In when Web1.GotText url responseCode responseType responseContent → if responseCode = 200 then call convertWith responseContent else set Label4.Text to "Could not load the rate — using sample data"; call convertWithSample. Procedure convertWith jsonText: find "USD": with find, segment the number after it up to the next } or comma, set global rate to that number, set Label2.Text to join "Rate: 1 THB = " + get global rate + " USD (live)", set Label3.Text to join TextBox1.Text + " THB = " + round (TextBox1.Text × get global rate × 100) ÷ 100 + " USD", set Label4.Text to "Live data from Frankfurter API". Procedure convertWithSample: set global rate to 0.028; set Label2.Text to "Rate: 1 THB = 0.028 USD (sample — not live)"; set Label3.Text to join TextBox1.Text + " THB = " + round (TextBox1.Text × 0.028 × 100) ÷ 100 + " USD (sample)"; set Label4.Text to "Sample data — the API did not reply"`. Note: the sample rate is only an example for practising the maths — the real rate changes daily.

3) Test: Enter 100 THB and tap Convert — check the result is about 2.8 USD with the live rate (or

the sample result, clearly labelled). Turn Wi-Fi off and check the sample fallback appears. 90-minute timing: 0–10 plan/sketch — work out 100 THB in USD on paper first, then compare with the app; 10–20 demo — Rica shows the raw API reply and points out the rate number inside it; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test live, test offline fallback, test a second amount; 80–90 share — convert the price of a snack from THB to USD and check it against the paper maths. Test checklist: A live rate appears when online; the conversion maths matches a hand calculation; offline shows the sample result clearly labelled as sample; an empty amount shows the warning. Common bug: the result is wildly wrong (e.g. 100 THB = 2800 USD) — fix: check the extracted number is the USD rate (about 0.028), not the THB amount, and that the multiply uses the TextBox number as a number (NumbersOnly on the TextBox). Success check: Gin can convert THB to USD with a fetched rate and say honestly whether the rate is live or sample data. Homework: Add a second conversion (THB → EUR) using to=EUR in the same API call pattern, or convert his weekly pocket money.

Session 64News / facts app — fetch a list from a public API, display itWed 2 Feb 2028
Wed 2 Feb 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 2 Feb 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can fetch a list of items from a public API and display them in a ListView, tapping one to see its details. Components: Screen1 — Label1, Text "Facts & News", FontSize 20, Bold true; Button1, Text "Load facts", FontSize 18; ListView1, FontSize 16; Label2, Text "", FontSize 16; Label3, Text "", FontSize 14; Web1 (non-visible). Step-by-step build:

1) Designer setup: Add the title label, the Load facts button, ListView1 for the items, a details

label (Label2) and a status label (Label3). Add Web1. What is needed: internet and a public API that returns a list with no key. Do not invent a key or a news source. The honest plan: use a free, no-key facts API — e.g. https://uselessfacts.jsph.pl/api/v2/facts/random?language=en returns one random fact, and for a list use the Open Trivia Database, https://opentdb.com/api.php?amount=5&type=multiple, which returns 5 quiz questions with no key. If either is unreachable or its format has changed by the session date, use the fallback: a built-in sample list stored in a variable — e.g. "Honey never spoils.", "Octopuses have three hearts.", "Bananas are berries." — shown in the ListView and labelled "Sample facts — the API did not reply". Do not present sample facts as fetched news.

2) Blocks setup: Make global variables factsList = create empty list and detailsList =

create empty list. In when Button1.Click → set Label3.Text to "Loading…"; set Web1.Url to "https://opentdb.com/api.php?amount=5&type=multiple"; call Web1.Get. In when Web1.GotText url responseCode responseType responseContent → if responseCode = 200 then call showItems responseContent else set Label3.Text to "Could not load — showing sample facts"; call showSampleFacts. Procedure showItems jsonText: the reply is JSON; App Inventor has no built-in JSON parser, so extract the 5 questions with text blocks — find each "question":" with find, segment the text up to the next ",", and add it to factsList; add the matching "correct_answer":" value to detailsList in the same step. Then set ListView1.Elements to get global factsList and set Label3.Text to "Live data from Open Trivia DB". Note: questions may contain HTML codes like &quot; — tell Gin these are part of web text and the app shows them as-is. Procedure showSampleFacts: set global factsList to make a list "Honey never spoils." "Octopuses have three hearts." "Bananas are berries." "A day on Venus is longer than its year." "Sharks existed before trees."; set ListView1.Elements to get global factsList; set Label3.Text to "Sample facts — the API did not reply". In when ListView1.AfterPicking → set Label2.Text to join "Answer: " + select list item list get global detailsList index ListView1.SelectionIndex (for sample facts, set Label2 to "Sample fact — tap Load facts to try the live list.").

3) Test: Tap Load facts and check 5 real questions appear; tap one and check its answer shows. Turn

Wi-Fi off and check the 5 sample facts appear, clearly labelled. 90-minute timing: 0–10 plan/sketch — discuss what "news" means vs a fact list, and why a key-free API is used; 10–20 demo — Rica shows the raw API reply and points out one question inside it; 20–65 build — Designer + Blocks as above; 65–80 test & fix — test live, test offline fallback, tap each item; 80–90 share — read out the best fact or question to Ray and Run and say whether it was live or sample. Test checklist: Live load shows 5 real items from the API; tapping one shows its detail/answer; offline shows the 5 sample facts labelled as sample; the app never claims sample data is live. Common bug: the ListView shows blank or garbled items — fix: re-read the raw reply in a label first to check the real format (field names and quotes change between APIs), and check the find text matches it exactly; if parsing is too fragile, fall back to showing the whole reply text in a scrollable label instead of a parsed list. Success check: Gin can load a list from a public API, tap an item to see its detail, and say honestly whether the list is live or sample data. Homework: Add a second button "Load one random fact" using the Useless Facts API and show the single fact in Label2.

Session 65QR code — generate / scan a code with BarcodeScannerWed 9 Feb 2028
Wed 9 Feb 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 9 Feb 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can scan a QR code with BarcodeScanner and show its text, and generate a QR image for his own text using a web service. Components: LabelTitle, Text "QR Scanner"; ButtonScan, Text "Scan QR Code", FontSize 18; LabelResult, Text "Result will appear here", FontSize 16; TextBoxText, Hint "Type text to turn into a QR code, e.g. V = I × R"; ButtonMake, Text "Make QR Code", FontSize 18; ImageQR, Picture "", Width 200, Height 200; BarcodeScanner1 (non-visible); Web1 (non-visible, Url blank). Step-by-step build:

1) Designer setup: add the labels, buttons, TextBox and Image above in a vertical layout; set Screen1 Title to "QR Code App"; drag in BarcodeScanner1 and Web1 from Sensors / Connectivity.

2) Blocks setup — scan: when ButtonScan.Click → call BarcodeScanner1.DoScan — then when BarcodeScanner1.AfterScan result → set LabelResult.Text to result and set LabelResult.Text to join "Scanned: " + result.

3) Blocks setup — generate: when ButtonMake.Click → if TextBoxText.Text = "" then set LabelResult.Text to "Type something first" else set Web1.Url to join "https://api.qrserver.com/v1/create-qr-code/?size=200x200&data=" + TextBoxText.Text then call Web1.Get.

4) Blocks setup — show image: when Web1.GotText responseCode responseContent → if responseCode = 200 then set ImageQR.Picture to Web1.Url else set LabelResult.Text to "Could not make the QR code — check internet". Note: this uses the public QR image URL directly; if the site is blocked, use the fallback below.

5) Test: scan a printed QR code (e.g. one made on Rica's laptop, or a QR on a book/poster); type "10Ω + 20Ω = 30Ω" and make its QR, then scan it back with the same app.

90-minute timing: 0–10 plan/sketch — draw the scan screen and the make-QR screen; 10–20 demo — Rica scans a code live; 20–65 build — scan first, then generate; 65–80 test & fix — scan 3 different codes; 80–90 share — Gin shows Rica a QR he made and what it decodes to. Test checklist: Tap Scan → camera opens → point at a QR code → result text appears in LabelResult. Type text → tap Make QR Code → image appears. Common bug: camera permission denied or scan returns nothing — fix: allow camera permission in phone settings, hold the phone steady 20 cm away, use a larger printed code in good light. Success check: Gin scans a QR code and displays its text, and generates a QR image from his own typed text. Homework: Make a QR code for "Ohm's Law: V = I × R" and bring it (printed or on screen) to scan next week. Needs / fallback: Needs a phone camera and internet for generating the QR image; scanning itself works offline once the app is installed. If there is no internet, skip step 4 and practise scanning only, or swap to a polish session on an earlier app.

Session 66Sharing — share text / image to another appWed 16 Feb 2028
Wed 16 Feb 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 16 Feb 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can share text and an image from his app to another app (e.g. Notes, Messenger, email) using the Sharing component. Components: LabelTitle, Text "Share My Result"; LabelResult, Text "V = I × R — I = 2 A, R = 10 Ω, V = 20 V", FontSize 16; TextBoxMessage, Hint "Type a message to share"; ButtonShareText, Text "Share Text", FontSize 18; ButtonShareImage, Text "Share Image", FontSize 18; ImageShare, Picture "resistor.png" (use an image already in Media, or a photo taken in Session 44); LabelStatus, Text ""; Sharing1 (non-visible). Step-by-step build:

1) Designer setup: add the labels, TextBox, two buttons and Image above; upload one image to Media (a resistor photo or a screenshot from an earlier app) and set ImageShare.Picture to it.

2) Blocks setup — share text: when ButtonShareText.Click → if TextBoxMessage.Text = "" then call Sharing1.ShareMessage LabelResult.Text else call Sharing1.ShareMessage TextBoxMessage.Text — then set LabelStatus.Text to "Sharing menu opened".

3) Blocks setup — share image: when ButtonShareImage.Click → call Sharing1.ShareFile ImageShare.Picture — then set LabelStatus.Text to "Choose an app to share the image". Note: ShareFile needs a real file path; if it fails, use ShareMessage with the text instead (see fallback).

4) Blocks setup — preset result: add when Screen1.Initialize → set LabelResult.Text to "My Ohm's Law result: V = 20 V (I = 2 A, R = 10 Ω)" so there is always something ready to share.

5) Test: tap Share Text → pick Notes or Messenger in the Android share sheet → check the text arrives; tap Share Image → pick an app → check the image arrives.

90-minute timing: 0–10 plan/sketch — list what is worth sharing from his apps (a quiz score, a calculator result); 10–20 demo — Rica shares text from a phone; 20–65 build — text share first, image share second; 65–80 test & fix — share to two different apps; 80–90 share — Gin shares his Ohm's Law result to Rica's phone/app of her choice. Test checklist: Tap Share Text → Android share sheet appears → chosen app receives the exact text. Tap Share Image → image appears in the chosen app. Common bug: ShareFile shows "file not found" — fix: check ImageShare.Picture is a file in Media (not a web URL); if it still fails, share the text version and note it — do not invent a file path. Success check: Gin shares both a text result and an image from his app into another app. Homework: Share one calculator result from an earlier app as text to Rica (or to himself in Notes) and note which app he used. Needs / fallback: Needs a phone with at least one other app that accepts shared text/images (Notes, Messenger, email). No account or API key needed. If ShareFile fails on the device, the text-share version counts as the success for this session.

Session 67Web viewer — show a safe website inside the appWed 23 Feb 2028
Wed 23 Feb 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 23 Feb 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can show a safe website inside his app with WebViewer, with buttons to go to chosen pages and back. Components: LabelTitle, Text "Web Viewer"; ButtonHome, Text "Home", FontSize 16; ButtonElectronics, Text "Electronics Help", FontSize 16; ButtonPortfolio, Text "My Portfolio", FontSize 16; WebViewer1, Width Fill parent, Height 400; LabelStatus, Text ""; ButtonBack, Text "← Back", FontSize 16; ButtonForward, Text "Forward →", FontSize 16. Step-by-step build:

1) Designer setup: add the buttons in a row at the top, WebViewer1 below them, Back/Forward buttons and LabelStatus underneath; set Screen1 Title to "Web Viewer App".

2) Blocks setup — go to a page: when ButtonElectronics.Click → call WebViewer1.GoToUrl "https://en.wikipedia.org/wiki/Ohm%27s_law" and set LabelStatus.Text to "Loading Ohm's Law…".

3) Blocks setup — portfolio: when ButtonPortfolio.Click → call WebViewer1.GoToUrl "https://ricamaesupa-portfolio.pages.dev/" — this is Rica's portfolio site, a safe known page. when ButtonHome.Click → call WebViewer1.GoToUrl "https://www.google.com" — or a start page Rica approves.

4) Blocks setup — navigation: when ButtonBack.Click → call WebViewer1.GoBack and when ButtonForward.Click → call WebViewer1.GoForward; add when WebViewer1.PageLoaded url → set LabelStatus.Text to join "Loaded: " + url.

5) Test: tap each button, wait for the page, tap Back then Forward, and check LabelStatus shows the loaded address.

90-minute timing: 0–10 plan/sketch — list 3 safe pages to include and why; 10–20 demo — Rica shows a WebViewer loading a page; 20–65 build — buttons first, navigation second; 65–80 test & fix — load each page twice, test Back/Forward; 80–90 share — Gin shows Rica his viewer loading the Ohm's Law page. Test checklist: Each button loads its page inside the app (not in the phone browser). Back returns to the previous page; Forward goes ahead again. Common bug: page stays blank — fix: check internet is on, check the URL starts with https:// and has no spaces, try the portfolio URL which is known to work. Success check: Gin's app loads at least two safe websites inside WebViewer and Back/Forward work. Homework: Choose one more safe electronics page (with Rica's approval) to add as a fourth button next session. Needs / fallback: Needs internet and Rica-approved URLs only — Gin must not browse to unapproved sites in the session. If there is no internet, build the buttons and navigation blocks with the URLs typed in, test the layout offline, and load the pages next week.

Session 68Online quiz — fetch questions from the web, play themWed 1 Mar 2028
Wed 1 Mar 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 1 Mar 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can fetch a list of quiz questions from the web with the Web component and play them one by one in his app. Components: LabelTitle, Text "Online Quiz"; LabelQuestion, Text "Tap Load Quiz to start", FontSize 18; ButtonA, Text "A", FontSize 16; ButtonB, Text "B", FontSize 16; ButtonC, Text "C", FontSize 16; ButtonD, Text "D", FontSize 16; LabelScore, Text "Score: 0", FontSize 16; ButtonLoad, Text "Load Quiz", FontSize 18; LabelFeedback, Text ""; Web1 (non-visible); global variable questions (empty list), currentQuestion (number, 1), score (number, 0). Step-by-step build:

1) Designer setup: add the labels and four answer buttons in a vertical layout; set Screen1 Title to "Online Quiz"; drag in Web1.

2) Blocks setup — load: when ButtonLoad.Click → set Web1.Url to [the quiz URL Rica gives on the day — a public sample quiz file, e.g. a small JSON/text list hosted where Rica can see it] → call Web1.Get and set LabelQuestion.Text to "Loading…". Do not invent a quiz API URL in advance — use the URL Rica supplies, or the offline fallback below.

3) Blocks setup — receive: when Web1.GotText responseCode responseContent → if responseCode = 200 then set global questions to [parse responseContent into a list — for a simple text list, split at "\n"; for JSON, use the Web JSONTextDecode block] → call procedure showQuestion else set LabelQuestion.Text to "Could not load — using offline questions" → call procedure loadOfflineQuestions.

4) Blocks setup — show and answer: procedure showQuestion → set LabelQuestion.Text to select list item global questions global currentQuestion (with question + 4 answers stored as a sub-list: item 1 = question, items 2–5 = answers, item 6 = correct letter) → set ButtonA.Text to item 2, ButtonB.Text to item 3, and so on. when ButtonA.Click → call procedure checkAnswer "A"; repeat for B, C, D.

5) Blocks setup — check: procedure checkAnswer letter → if letter = [correct letter for this question] then set global score to global score + 1 → set LabelFeedback.Text to "Correct!" else set LabelFeedback.Text to "Not quite — the answer was …" → set LabelScore.Text to join "Score: " + global score → set global currentQuestion to global currentQuestion + 1 → call procedure showQuestion.

6) Test: tap Load Quiz, answer all questions, check the score updates and the next question appears.

90-minute timing: 0–10 plan/sketch — draw the quiz screen and the question format; 10–20 demo — Rica shows a fetched question list; 20–65 build — offline quiz first (so the game works), then the Web fetch; 65–80 test & fix — play a full round online, then offline; 80–90 share — Gin plays one round for Rica and explains where the questions came from. Test checklist: Tap Load Quiz → questions appear (not "Loading…" forever). Tap an answer → feedback and score update → next question shows. Common bug: questions show as one long block of text — fix: check the split/parsing step (split at newline, or check the JSON structure) and test with the offline list first. Success check: Gin plays a quiz whose questions came from the web, with score tracking. Homework: Write 5 new electronics questions (question + 4 answers + correct letter) in the same list format for next week. Needs / fallback: Needs internet and a quiz source URL supplied/approved by Rica on the day — no API key is invented here. Fallback (use it if the fetch fails): procedure loadOfflineQuestions sets global questions to a built-in list of 5 electronics questions Gin writes himself (e.g. "What is V when I = 2 A and R = 10 Ω? / 5 V / 10 V / 20 V / 40 V / C"), and the same show/check blocks run unchanged.

Session 69Send data to the web — post a score / reading (exploration)Wed 8 Mar 2028
Wed 8 Mar 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 8 Mar 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can send a small piece of data (a quiz score or a voltage reading) from his app to the web with Web.PostText, and see whether it arrived. Components: LabelTitle, Text "Send My Score"; TextBoxName, Hint "Your name"; LabelScore, Text "Score: 8 / 10", FontSize 16; TextBoxReading, Hint "Voltage reading, e.g. 20"; ButtonSend, Text "Send to the Web", FontSize 18; LabelStatus, Text "Not sent yet", FontSize 16; Web1 (non-visible). Step-by-step build:

1) Designer setup: add the labels, TextBoxes and ButtonSend above; set Screen1 Title to "Send Data"; drag in Web1. Rica decides on the day where the data goes — a test form/endpoint she controls or a public test endpoint she approves. No real account, password or API key is used.

2) Blocks setup — build the message: when ButtonSend.Click → if TextBoxName.Text = "" then set LabelStatus.Text to "Type your name first" else set Web1.Url to [Rica's approved test URL] → call Web1.PostText join "name=" + TextBoxName.Text + "&score=8&voltage=" + TextBoxReading.Text and set LabelStatus.Text to "Sending…".

3) Blocks setup — confirm: when Web1.GotText responseCode responseContent → if responseCode = 200 then set LabelStatus.Text to "Sent! The web replied." else set LabelStatus.Text to join "Did not send — code " + responseCode.

4) Blocks setup — local record too: after a successful send, also call TinyDB1.StoreValue tag "lastSentScore" valueToStore LabelScore.Text — add TinyDB1 (non-visible) so the score is kept on the phone even if the web send fails.

5) Test: type a name and a reading (e.g. 20 V), tap Send, read LabelStatus, then check with Rica whether the test endpoint received it.

90-minute timing: 0–10 plan/sketch — what data is safe to send (a score, a reading — never a password, address or full name of someone else); 10–20 demo — Rica shows a test send and its reply; 20–65 build — message first, send second, local save third; 65–80 test & fix — send twice with different readings; 80–90 share — Gin explains what he sent, where it went, and what the reply said. Test checklist: Tap Send with a name filled in → LabelStatus changes to "Sending…" then "Sent!". Tap Send with the name empty → warning appears and nothing is sent. Common bug: response code is not 200 — fix: check the URL Rica gave (copy it exactly), check internet, and check the local TinyDB copy saved anyway. Success check: Gin sends a score/reading to the web and can show the reply status, plus a local TinyDB copy. Homework: Write down, in one sentence, what data should never be sent from an app (passwords, addresses, other people's details). Needs / fallback: Exploration — needs internet and a test endpoint Rica supplies/approves on the day; no API key, account or real server is invented here. Fallback: if no endpoint is available, PostText to the test URL is replaced by saving the same text to TinyDB and showing "Saved on phone — web send practised with sample data", and the session counts as the logic learned, not a live send.

Session 70Connectivity: offline vs online — what works without internet?Wed 15 Mar 2028
Wed 15 Mar 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 15 Mar 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can test each of his connected apps with internet off and on, and sort them into "works offline" and "needs internet". Components: LabelTitle, Text "Offline or Online?"; ListViewApps, ElementsFromString "QR Scanner, Sharing, Web Viewer, Online Quiz, Send Data, Bluetooth Chat"; LabelResult, Text "Tap an app to test it", FontSize 16; ButtonTestOffline, Text "Test: Internet OFF", FontSize 16; ButtonTestOnline, Text "Test: Internet ON", FontSize 16; LabelTable, Text "Offline: — | Online only: —", FontSize 16; TinyDB1 (non-visible, to save the table). Step-by-step build:

1) Designer setup: add the ListView with the six app names above, the two test buttons, and the two labels; set Screen1 Title to "Offline vs Online".

2) Blocks setup — pick an app: when ListViewApps.AfterPicking → set LabelResult.Text to join "Testing: " + ListViewApps.Selection and set global selectedApp to ListViewApps.Selection (global variable selectedApp, text, "").

3) Blocks setup — record the result: when ButtonTestOffline.Click → if global selectedApp = "" then set LabelResult.Text to "Pick an app first" else set LabelResult.Text to join global selectedApp + " — try it now with Wi-Fi/mobile data OFF, then tap Got Result" — add ButtonGotResult, Text "Got Result — It Worked" and ButtonFailed, Text "It Did Not Work"; when ButtonGotResult.Click → call procedure addToList "Offline"; when ButtonFailed.Click → call procedure addToList "Online only".

4) Blocks setup — save the table: procedure addToList group → set LabelTable.Text to join LabelTable.Text + "\n" + global selectedApp + " — " + group → call TinyDB1.StoreValue tag global selectedApp valueToStore group. when ButtonTestOnline.Click → set LabelResult.Text to "Now turn internet ON and re-test the same app".

5) Test: turn internet off (Rica helps — aeroplane mode or Wi-Fi off), open the real QR Scanner and Calculator apps from earlier sessions, note what works; turn internet on, re-test the Web Viewer and Online Quiz.

90-minute timing: 0–10 plan/sketch — predict for each app: offline or online?; 10–20 demo — Rica turns internet off and shows one app failing and one working; 20–65 build — the tester app, then the real tests; 65–80 test & fix — test all six apps both ways, fill the table; 80–90 share — Gin reads out his finished table and explains one surprise. Test checklist: With internet off: Calculator / QR scan / Sharing to Notes still work; Web Viewer / Online Quiz / Send Data do not. With internet on: all six work. Common bug: the phone still uses mobile data after Wi-Fi is off — fix: use aeroplane mode (and note Bluetooth still works in aeroplane mode if switched back on), and re-test. Success check: Gin produces a saved offline/online table for all six apps, tested both ways. Homework: Add one more app from an earlier phase (e.g. his quiz or timer) to the table and test it at home with Wi-Fi off. Needs / fallback: Needs a phone where Rica can switch internet off/on, and Gin's earlier apps installed via Companion. No internet is needed for the offline half by design. If a test app is missing, test its blocks in the Companion with a sample value instead of the live app.

Session 71Connectivity app — combine Bluetooth + Web in one helperWed 22 Mar 2028
Wed 22 Mar 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 22 Mar 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can build one helper app that uses Bluetooth (send a short message) and Web (fetch a value) on separate screens, with a menu to switch between them. Components: Screen1 (Menu): LabelTitle, Text "Connectivity Helper"; ButtonBluetooth, Text "Bluetooth", FontSize 18; ButtonWeb, Text "Web", FontSize 18; ButtonStatus, Text "Status", FontSize 18. ScreenBluetooth: LabelBT, Text "Bluetooth Chat"; TextBoxBTMessage, Hint "Type a message"; ButtonBTSend, Text "Send by Bluetooth", FontSize 18; LabelBTStatus, Text "Not connected"; BluetoothClient1 (non-visible). ScreenWeb: LabelWeb, Text "Web Lookup"; ButtonWebFetch, Text "Fetch Value", FontSize 18; LabelWebResult, Text ""; Web1 (non-visible). ScreenStatus: LabelStatusAll, Text "Bluetooth: — | Web: —". Step-by-step build:

1) Designer setup: add Screen1, ScreenBluetooth, ScreenWeb, ScreenStatus; put the menu buttons on Screen1, the Bluetooth controls on ScreenBluetooth, the Web controls on ScreenWeb, and the status label on ScreenStatus; set each screen's Title.

2) Blocks setup — menu: when ButtonBluetooth.Click → open another screen screenName "ScreenBluetooth"; same for ButtonWeb → "ScreenWeb" and ButtonStatus → "ScreenStatus"; on each sub-screen add ButtonBackToMenu, Text "← Menu" with when ButtonBackToMenu.Click → close screen.

3) Blocks setup — Bluetooth: when ScreenBluetooth.Initialize → if BluetoothClient1.IsConnected then set LabelBTStatus.Text to "Connected" else set LabelBTStatus.Text to "Not connected — pair first (see Session 58)"; when ButtonBTSend.Click → if BluetoothClient1.IsConnected then call BluetoothClient1.SendText TextBoxBTMessage.Text → set LabelBTStatus.Text to "Sent!" else set LabelBTStatus.Text to "Not connected".

4) Blocks setup — Web: when ButtonWebFetch.Click → set Web1.Url to [a small public value Rica approves on the day, e.g. the same quiz/weather sample URL used in Sessions 62–64] → call Web1.Get; when Web1.GotText responseCode responseContent → if responseCode = 200 then set LabelWebResult.Text to responseContent else set LabelWebResult.Text to "Fetch failed — check internet".

5) Blocks setup — status: when ScreenStatus.Initialize → set LabelStatusAll.Text to join "Bluetooth: " + [if BluetoothClient1.IsConnected then "connected" else "not connected"] + " | Web: " + LabelWebResult.Text.

6) Test: from the menu open Bluetooth, send "Hello from Gin" to a paired phone (or note "not connected" honestly); open Web, fetch the value; open Status and read both lines.

90-minute timing: 0–10 plan/sketch — draw the menu and three screens; 10–20 demo — Rica opens a multi-screen app and switches screens; 20–65 build — menu + screens first, Bluetooth second, Web third; 65–80 test & fix — test each screen twice; 80–90 share — Gin demos the full helper to Rica, switching screens live. Test checklist: Menu buttons open the right screen; Back returns to the menu. Bluetooth send works when paired, and shows "Not connected" (not a crash) when not paired. Web fetch shows a value or a clear failure message. Common bug: opening a screen by the wrong name — fix: check the screenName text matches the screen name exactly, including capital letters. Success check: Gin's helper app has a working menu, a Bluetooth screen and a Web screen, and a status screen reporting both. Homework: Sketch one more screen to add to the helper (e.g. a QR screen) and list its components. Needs / fallback: Needs a second paired Bluetooth phone for the live Bluetooth test (see Sessions 57–58); needs internet and a Rica-approved URL for the Web fetch. Fallback: if no second phone is available, the Bluetooth screen is tested with the "Not connected" message and a typed sample message, and the Web screen carries the session — do not invent a successful Bluetooth send.

Session 72Connectivity showcase — test all connected apps, fix connection bugsWed 29 Mar 2028
Wed 29 Mar 2028 | Phase 5 — Connectivity: Bluetooth & Web APIs

Date: Wed 29 Mar 2028 | Phase: Phase 5 — Connectivity: Bluetooth & Web APIs Learning objective: Gin can playtest all his Phase 5 apps (Sessions 57–71), list every connection bug, fix the most important ones, and pick his best connected app. Components: LabelTitle, Text "Connectivity Showcase"; ListViewApps, ElementsFromString "Bluetooth Chat, Bluetooth Remote, Web Basics, Weather App, Online Quiz, QR Scanner, Sharing, Web Viewer, Connectivity Helper"; LabelNotes, Text "Bug list:", FontSize 16; TextBoxBug, Hint "Type a bug, e.g. Weather shows nothing when offline"; ButtonAddBug, Text "Add Bug", FontSize 16; ButtonFixed, Text "Mark Fixed", FontSize 16; LabelBest, Text "My best connected app: —"; TinyDB1 (non-visible, tag "phase5Bugs"). Step-by-step build:

1) Designer setup: add the ListView of Phase 5 apps, the bug TextBox and buttons, and the labels above; set Screen1 Title to "Connectivity Showcase".

2) Blocks setup — bug list: when ButtonAddBug.Click → if TextBoxBug.Text = "" then set LabelNotes.Text to "Type the bug first" else set LabelNotes.Text to join LabelNotes.Text + "\n• " + TextBoxBug.Text → call TinyDB1.StoreValue tag "phase5Bugs" valueToStore LabelNotes.Text → set TextBoxBug.Text to "".

3) Blocks setup — load saved bugs: when Screen1.Initialize → set LabelNotes.Text to call TinyDB1.GetValue tag "phase5Bugs" valueIfTagNotThere "Bug list:".

4) Blocks setup — pick the best: when ListViewApps.AfterPicking → set LabelBest.Text to join "My best connected app: " + ListViewApps.Selection — Gin picks only after testing each app.

5) Test (the main work of the session): open each Phase 5 app in Companion, test it once online and once offline (Session 70 table), write each bug into TextBoxBug, fix the top 3 bugs in the original apps (e.g. a missing "check internet" message, a wrong URL, a Bluetooth "not connected" crash), and re-test.

90-minute timing: 0–10 plan/sketch — list the 9 apps and the order to test them; 10–20 demo — Rica tests one app and logs one bug; 20–65 build + test — test apps in order, log bugs, fix the top 3; 65–80 test & fix — re-test the fixed apps; 80–90 share — Gin presents his best connected app and reads his bug list. Test checklist: Every Phase 5 app opened at least once; each bug written down before it is fixed; the top 3 bugs fixed and re-tested. Common bug: an app that worked last week now shows a blank Web result — fix: check the URL was not changed, check internet, and check the GotText responseCode branch exists (Session 68 pattern). Success check: Gin has a saved bug list for Phase 5, at least 3 bugs fixed and re-tested, and a named best connected app. Homework: Back up all Phase 5 project files (.aia) with Rica and write one sentence for each app: what it needs (Bluetooth / internet / camera / nothing). Needs / fallback: Needs Gin's Phase 5 apps, a phone, and internet for the online tests. Fallback: any app that cannot be tested live (e.g. no second Bluetooth phone) is marked "not tested — needs a second phone" in the bug list instead of being marked as working — do not invent a pass.

Session 73AI basics — what a classifier does, train vs test (concept, blocks only)Wed 5 Apr 2028
Wed 5 Apr 2028 | Phase 6 — AI & Smart Apps

Date: Wed 5 Apr 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can explain in his own words what a classifier does, and show the difference between training (teaching with examples) and testing (trying a new example) using blocks only. (Exploration — AI topics are Rica's exploration, not a CIY-assigned track.) Components: LabelTitle, Text "What Is a Classifier?"; ButtonTrain, Text "Train: Show Examples", FontSize 18; ButtonTest, Text "Test: Try a New One", FontSize 18; LabelExplain, Text "Tap Train, then Test", FontSize 16; LabelTrainCount, Text "Examples shown: 0"; LabelTestResult, Text ""; ListViewExamples, ElementsFromString "Red resistor — 10 Ω, Brown resistor — 100 Ω, Yellow resistor — 10 kΩ"; global variable trainedExamples (empty list), testAnswer (text, ""). Step-by-step build:

1) Designer setup: add the labels, two buttons and ListView above; set Screen1 Title to "AI Basics"; draw on paper first: a box labelled "Classifier", arrows in (examples) and out (a guess).

2) Blocks setup — train: when ButtonTrain.Click → set global trainedExamples to ListViewExamples.Elements → set LabelTrainCount.Text to join "Examples shown: " + length of list global trainedExamples → set LabelExplain.Text to "Training = showing examples. The classifier learns the pattern from these."

3) Blocks setup — test: when ButtonTest.Click → if length of list global trainedExamples = 0 then set LabelTestResult.Text to "Train first — a classifier with no examples can only guess" else set LabelTestResult.Text to "Test = a NEW example. The classifier guesses from what it learned — it can be wrong!".

4) Blocks setup — a simple rule-based "classifier" in blocks (no real AI yet): add TextBoxGuess, Hint "Type a colour, e.g. red"; ButtonGuess, Text "Guess"; when ButtonGuess.Click → if TextBoxGuess.Text = "red" then set LabelTestResult.Text to "Guess: 10 Ω resistor" else if TextBoxGuess.Text = "brown" then set LabelTestResult.Text to "Guess: 100 Ω resistor" else set LabelTestResult.Text to "I have not learned that colour yet".

5) Test: tap Train (count goes to 3), type "red" and tap Guess (correct guess), type "blue" and tap Guess ("not learned yet"), then discuss: a real classifier does the same thing, but learns the pattern itself instead of Gin writing each if/else.

90-minute timing: 0–10 plan/sketch — draw train vs test on paper; 10–20 demo — Rica shows a classifier guessing (right and wrong); 20–65 build — train/test buttons, then the rule-based guesser; 65–80 test & fix — try 5 colours, note which are learned and which are not; 80–90 share — Gin explains train vs test to Rica in one minute, using the resistor example. Test checklist: Tap Train → count shows 3 and explanation appears. Type "red" → guess "10 Ω". Type an unlearned colour → "not learned yet" (not a crash, not a made-up value). Common bug: Guess works before Train — fix: that is the point of the test, but add the if length = 0 check in step 3 so the app says so plainly. Success check: Gin can explain train vs test and show it with his blocks app. Homework: List 3 things a classifier could sort (resistors, fruits, hand-drawn shapes) and, for each, what 3 training examples he would show it. Needs / fallback: Needs no device, account, model or internet — this session is concept + blocks only, by design. If the Companion is unavailable, the whole session works on paper + the Blocks editor.

Session 74Image classifier 1 — Personal Image Classifier, train 2 classes (exploration)Wed 12 Apr 2028
Wed 12 Apr 2028 | Phase 6 — AI & Smart Apps

Date: Wed 12 Apr 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can train a Personal Image Classifier with two classes (e.g. "Resistor" and "Not resistor") using photos he takes himself. (Exploration.) Components: LabelTitle, Text "Train My Classifier"; ButtonClassA, Text "Train: Resistor", FontSize 16; ButtonClassB, Text "Train: Not Resistor", FontSize 16; LabelCountA, Text "Resistor photos: 0"; LabelCountB, Text "Not resistor photos: 0"; ButtonTrainModel, Text "Train Model", FontSize 18; LabelStatus, Text "Take photos to train each class"; Camera1 (non-visible); PersonalImageClassifier1 (non-visible, extension — add from Extensions; if it is not available on the day, use the fallback below). Step-by-step build:

1) Designer setup: add the labels and buttons above; set Screen1 Title to "Image Classifier 1". Rica checks on the day that the Personal Image Classifier extension is imported and that the phone camera works.

2) Blocks setup — collect class A: when ButtonClassA.Click → call Camera1.TakePicture — then when Camera1.AfterPicture image → call PersonalImageClassifier1.AddImage [image] class "Resistor" → set global countA to global countA + 1 → set LabelCountA.Text to join "Resistor photos: " + global countA. Add global variables countA and countB (numbers, 0).

3) Blocks setup — collect class B: same pattern with ButtonClassB, class "Not resistor", countB and LabelCountB. Aim for at least 10 photos per class: different angles, different light, different backgrounds — a classifier trained on 2 identical photos learns almost nothing.

4) Blocks setup — train: when ButtonTrainModel.Click → if global countA < 5 or global countB < 5 then set LabelStatus.Text to "Take at least 5 photos per class first" else call PersonalImageClassifier1.TrainClassifier → set LabelStatus.Text to "Training… wait for the Trained message".

5) Blocks setup — trained: when PersonalImageClassifier1.ClassifierTrained → set LabelStatus.Text to "Trained! Test it next session"; add when PersonalImageClassifier1.ClassifierError error → set LabelStatus.Text to join "Training problem: " + error.

6) Test: take 5+ photos per class, tap Train Model, wait for the Trained message, and save/export the model file if the extension offers it (Rica helps — keep the file for Session 75).

90-minute timing: 0–10 plan/sketch — choose the 2 classes and what counts as each; 10–20 demo — Rica trains a tiny 2-class model (or shows a video if the extension is missing); 20–65 build + photo-taking — collect photos for both classes; 65–80 test & fix — train, check the Trained message, retake blurry photos; 80–90 share — Gin shows Rica his photo counts and explains why varied photos matter. Test checklist: Each class has 5+ photos, counts update on screen. Tap Train Model → "Training…" then "Trained!" (not silence). Common bug: training never finishes or errors — fix: check there are photos in both classes, retake any photo that failed to save, and restart the Companion; do not claim the model is trained if no Trained message appeared. Success check: Gin has a 2-class classifier trained on his own photos, with the Trained message shown. Homework: Take 5 more photos per class at home (different light/background) ready to add next week. Needs / fallback: Needs a phone camera, the Personal Image Classifier extension imported, and time for training (training may need internet depending on the extension version — Rica checks on the day). Fallback: if the extension cannot be imported, do the session as a "paper + blocks" classifier — use the rule-based guesser from Session 73 with photo filenames as input, collect the photos into two labelled folders, and train the real model in Session 75 when the extension is ready. Do not invent a model file, a model URL, or a training result.

Session 75Image classifier 2 — train a third class, test accuracyWed 19 Apr 2028
Wed 19 Apr 2028 | Phase 6 — AI & Smart Apps

Date: Wed 19 Apr 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can add a third class to his classifier, retrain it, and test its accuracy by counting how many new photos it gets right. (Exploration.) Components: LabelTitle, Text "Classifier 2: Three Classes"; ButtonClassA, Text "Train: Resistor"; ButtonClassB, Text "Train: Not Resistor"; ButtonClassC, Text "Train: Wire / Cable", FontSize 16; LabelCountA, Text "Resistor: 0"; LabelCountB, Text "Not resistor: 0"; LabelCountC, Text "Wire: 0"; ButtonRetrain, Text "Retrain Model", FontSize 18; ButtonTestOne, Text "Test One Photo", FontSize 18; LabelAccuracy, Text "Correct: 0 / Tested: 0", FontSize 16; LabelLastGuess, Text ""; Camera1; PersonalImageClassifier1; global variables countA, countB, countC, correct, tested (numbers, 0). Step-by-step build:

1) Designer setup: add the three train buttons, three count labels, Retrain/Test buttons and accuracy labels above; load the Session 74 model if it was saved (Rica helps — import the model file, or retrain from the saved photos).

2) Blocks setup — third class: when ButtonClassC.Click → call Camera1.TakePicture — then when Camera1.AfterPicture image → call PersonalImageClassifier1.AddImage [image] class "Wire" → set global countC to global countC + 1 → set LabelCountC.Text to join "Wire: " + global countC. Keep adding to classes A and B with the Session 74 blocks until each class has at least 10 photos.

3) Blocks setup — retrain: when ButtonRetrain.Click → if global countA < 5 or global countB < 5 or global countC < 5 then set LabelAccuracy.Text to "Need 5+ photos in every class first" else call PersonalImageClassifier1.TrainClassifier.

4) Blocks setup — test one: when ButtonTestOne.Click → call Camera1.TakePicture — then on AfterPicture, call PersonalImageClassifier1.Classify [image]; add when PersonalImageClassifier1.ClassificationComplete result → set LabelLastGuess.Text to join "Guess: " + result → set global tested to global tested + 1 → [ask Gin: was it right? add ButtonRight, Text "✓ Right" and ButtonWrong, Text "✗ Wrong"].

5) Blocks setup — accuracy: when ButtonRight.Click → set global correct to global correct + 1 → call procedure showAccuracy; when ButtonWrong.Click → call procedure showAccuracy; procedure showAccuracy → set LabelAccuracy.Text to join "Correct: " + global correct + " / Tested: " + global tested.

6) Test: test 10 new photos (not the training photos), mark each Right/Wrong honestly, and read the final accuracy — e.g. 7/10. Discuss which class gets confused most.

90-minute timing: 0–10 plan/sketch — choose the third class and predict the accuracy; 10–20 demo — Rica tests one photo and marks it Right/Wrong; 20–65 build + photo-taking — third class photos, retrain; 65–80 test & fix — test 10 new photos, count accuracy; 80–90 share — Gin reports his accuracy and which class was hardest. Test checklist: Three classes each have 5+ photos; retrain shows a Trained message; 10 new photos tested with an honest Right/Wrong count. Common bug: the classifier always guesses the same class — fix: that class probably has far more photos, or the test photos look like the training photos; add more varied photos to the other classes and retrain — do not edit the result by hand. Success check: Gin has a 3-class classifier and a real accuracy count from 10 new photos. Homework: Take 5 photos that could confuse the classifier (e.g. a resistor next to a wire) and test them next week. Needs / fallback: Needs the Session 74 model/photos, a camera, and the classifier extension. Fallback: if the model file from Session 74 was not saved, retrain all three classes from scratch in this session (allow extra photo time, fewer test photos — 6 instead of 10). Never report an accuracy number that was not counted from real tests.

Session 76Classifier app — camera + classifier, show the result liveWed 26 Apr 2028
Wed 26 Apr 2028 | Phase 6 — AI & Smart Apps

Date: Wed 26 Apr 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can build a finished classifier app: point the camera, tap Classify, and see the result and confidence live on screen. (Exploration.) Components: LabelTitle, Text "What Is This?"; ImagePreview, Picture "", Width 250, Height 250; ButtonTakePhoto, Text "Take Photo", FontSize 18; ButtonClassify, Text "Classify!", FontSize 18; LabelResult, Text "Result: —", FontSize 20; LabelConfidence, Text "Confidence: —", FontSize 16; LabelHistory, Text "Last guesses:"; ButtonClear, Text "Clear", FontSize 16; Camera1; PersonalImageClassifier1; global variable lastImage (text, ""). Step-by-step build:

1) Designer setup: add the Image, buttons and labels above in a vertical layout; set Screen1 Title to "Classifier App"; load the trained 3-class model from Sessions 74–75 (Rica helps import it, or retrain quickly from saved photos).

2) Blocks setup — photo: when ButtonTakePhoto.Click → call Camera1.TakePicture; when Camera1.AfterPicture image → set ImagePreview.Picture to image → set global lastImage to image → set LabelResult.Text to "Photo ready — tap Classify!".

3) Blocks setup — classify: when ButtonClassify.Click → if global lastImage = "" then set LabelResult.Text to "Take a photo first" else call PersonalImageClassifier1.Classify global lastImage; when PersonalImageClassifier1.ClassificationComplete result → set LabelResult.Text to join "Result: " + result.

4) Blocks setup — confidence: if the extension returns a confidence/score list, add set LabelConfidence.Text to join "Confidence: " + [first score from the result] + "%" — if it returns only a class name, set LabelConfidence.Text to "Confidence: not shown by this version" and do not invent a percentage.

5) Blocks setup — history: after each result, set LabelHistory.Text to join LabelHistory.Text + "\n• " + result; when ButtonClear.Click → set LabelHistory.Text to "Last guesses:" → set LabelResult.Text to "Result: —" → set LabelConfidence.Text to "Confidence: —".

6) Test: classify a resistor, a wire, and a non-resistor object, and check the result + history update each time.

90-minute timing: 0–10 plan/sketch — draw the app screen (photo top, result big below); 10–20 demo — Rica classifies one object live; 20–65 build — photo + classify first, history second; 65–80 test & fix — classify 6 objects, note wrong guesses; 80–90 share — Gin demos the app to Ray and Run, classifying one object each. Test checklist: Take photo → image shows in ImagePreview. Tap Classify → result appears within a few seconds. History grows by one line per guess. Common bug: Classify tapped before a photo — fix: the if global lastImage = "" check in step 3 shows "Take a photo first" instead of crashing. Success check: Gin's app classifies a live camera photo and shows the result on screen. Homework: Classify 5 objects at home, write down the result and whether it was right, and bring the list. Needs / fallback: Needs the trained model from Sessions 74–75, a camera, and the classifier extension. Fallback: if the model will not load, use the rule-based guesser from Session 73 as the "classifier" for the demo (label it clearly as rules, not AI), and keep the camera + history parts — the app layout and flow are still learned.

Session 77Chatbot logic 1 — keyword replies, if / else chainsWed 3 May 2028
Wed 3 May 2028 | Phase 6 — AI & Smart Apps

Date: Wed 3 May 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can build a chatbot that replies to keywords with if/else blocks (e.g. "hello" → "Hi!"). (Exploration — rule-based logic, not a real AI model.) Components: LabelTitle, Text "Chatbot"; LabelChat, Text "Bot: Hi! Ask me something.", FontSize 16; TextBoxAsk, Hint "Type here, e.g. hello"; ButtonSend, Text "Send", FontSize 18; ButtonClear, Text "Clear Chat", FontSize 16; global variable chatText (text, "Bot: Hi! Ask me something."). Step-by-step build:

1) Designer setup: add LabelChat (Height 300, so the chat history fits), TextBoxAsk, Send and Clear buttons; set Screen1 Title to "Chatbot".

2) Blocks setup — send: when ButtonSend.Click → if TextBoxAsk.Text = "" then set LabelChat.Text to join LabelChat.Text + "\nBot: Type something first!" else set global chatText to join LabelChat.Text + "\nYou: " + TextBoxAsk.Text → set LabelChat.Text to global chatText → call procedure reply TextBoxAsk.Text → set TextBoxAsk.Text to "".

3) Blocks setup — reply (the if/else chain): procedure reply message → set local messageLower to call TextBoxAsk.Text [use the to lower case text block on message] → if messageLower contains "hello" or messageLower contains "hi" then set LabelChat.Text to join LabelChat.Text + "\nBot: Hi! How can I help?" else if messageLower contains "your name" then … + "\nBot: I am Gin's chatbot." else if messageLower contains "bye" then … + "\nBot: Goodbye! Come back soon." else … + "\nBot: I do not understand that yet — try hello.".

4) Blocks setup — clear: when ButtonClear.Click → set LabelChat.Text to "Bot: Hi! Ask me something.".

5) Test: type "hello", "what is your name", "bye", and a nonsense word — check each gets the right reply (or the honest "I do not understand" reply).

90-minute timing: 0–10 plan/sketch — list 5 keywords and their replies on paper; 10–20 demo — Rica chats with a simple keyword bot; 20–65 build — send + chat history first, reply chain second; 65–80 test & fix — try 8 messages, add any missing keyword; 80–90 share — Gin chats with his bot in front of Rica, showing a keyword that works and one that does not. Test checklist: Each keyword gives its own reply; an unknown word gives "I do not understand" (not a wrong confident answer, not a crash). Chat history grows correctly, newest at the bottom. Common bug: "Hello" with a capital H does not match — fix: the to lower case block in step 3, and use contains instead of = so "hello there" also matches. Success check: Gin's chatbot answers at least 4 keywords correctly and handles unknown words honestly. Homework: Add 3 new keywords + replies of his own (e.g. "thank you" → "You are welcome!"). Needs / fallback: Needs no device, account, model or internet — rule-based blocks only. If the Companion is unavailable, the whole session works in the Blocks editor + on paper.

Session 78Chatbot logic 2 — lists of replies, random answersWed 10 May 2028
Wed 10 May 2028 | Phase 6 — AI & Smart Apps

Date: Wed 10 May 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can make his chatbot less repetitive by storing replies in lists and picking one at random. (Exploration — rule-based logic, not a real AI model.) Components: LabelTitle, Text "Chatbot 2: Random Replies"; LabelChat, Text "Bot: Hi again!", FontSize 16, Height 300; TextBoxAsk, Hint "Type here"; ButtonSend, Text "Send", FontSize 18; ButtonClear, Text "Clear Chat", FontSize 16; global variables helloReplies (list: "Hi!", "Hello there!", "Hey! Nice to see you."), jokeReplies (list: "Why did the resistor go to school? To get more resistance!", "I would tell you an Ohm's Law joke, but it is too revolting."), unknownReplies (list: "I do not know that one yet.", "Hmm, try asking about hello or a joke.", "Not sure — can you say it another way?"). Step-by-step build:

1) Designer setup: copy the Session 77 chatbot screen (or open the same project and add to it); add the three list variables in Blocks as initialize global helloReplies to create empty list + add items to list blocks with the texts above.

2) Blocks setup — random pick: procedure pickRandom listToPickFrom → set local answer to select list item listToPickFrom random integer from 1 to length of list listToPickFrom → return local answer (use a procedure with a result).

3) Blocks setup — reply with lists: procedure reply message → set local lower to [message in lower case] → if lower contains "hello" or lower contains "hi" then set LabelChat.Text to join LabelChat.Text + "\nBot: " + call pickRandom global helloReplies else if lower contains "joke" then … + call pickRandom global jokeReplies else … + call pickRandom global unknownReplies.

4) Blocks setup — send/clear: reuse Session 77: when ButtonSend.Click → [add "You: …" to chat, call reply, clear TextBox]; when ButtonClear.Click → reset LabelChat.Text.

5) Test: type "hello" 5 times — the reply should change sometimes, not repeat identically every time; type "joke" 3 times — check both jokes appear; type nonsense — check the unknown replies vary.

90-minute timing: 0–10 plan/sketch — write 3 replies per keyword on paper; 10–20 demo — Rica shows the same keyword giving different replies; 20–65 build — lists first, random procedure second, reply chain third; 65–80 test & fix — test each keyword 5 times, fix any list that only ever gives one reply; 80–90 share — Gin shows Rica the bot answering "hello" three times with (probably) different replies. Test checklist: "hello" × 5 gives at least 2 different replies. "joke" gives a joke from the list (not a made-up one). Unknown words give a varied honest reply. Common bug: random always picks the first item — fix: check the random integer from 1 to length of list block uses the list length (not a fixed 1), and that the list actually has 3 items. Success check: Gin's chatbot gives varied replies from lists, picked at random. Homework: Add a third keyword list of his own (e.g. "bye" with 3 different farewells). Needs / fallback: Needs no device, account, model or internet — lists + random blocks only. Fallback if random feels too unpredictable for a demo: add a counter so replies rotate in order (1st, 2nd, 3rd, then back to 1st) instead of random — same lists, different picker.

Session 79Chatbot: electronics helper — ask about Ohm's Law, get an answerWed 17 May 2028
Wed 17 May 2028 | Phase 6 — AI & Smart Apps

Date: Wed 17 May 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can build an electronics helper chatbot that answers Ohm's Law and resistor questions from keywords and does the maths in blocks. (Exploration — rule-based logic, not a real AI model.) Components: LabelTitle, Text "Electronics Helper Bot"; LabelChat, Text "Bot: Ask me about Ohm's Law or resistors!", FontSize 16, Height 300; TextBoxAsk, Hint "e.g. What is V when I = 2 and R = 10?"; ButtonSend, Text "Send", FontSize 18; TextBoxI, Hint "Current I (A)"; TextBoxR, Hint "Resistance R (Ω)"; ButtonCalcV, Text "Calculate V = I × R", FontSize 16; LabelCalc, Text ""; global variable vAnswer (number, 0). Step-by-step build:

1) Designer setup: add the chat labels/buttons from Session 77–78, plus the I/R TextBoxes, Calculate button and LabelCalc; set Screen1 Title to "Electronics Helper".

2) Blocks setup — keyword answers: procedure reply message → set local lower to [message in lower case] → if lower contains "ohm" and lower contains "law" then Bot: "Ohm's Law: V = I × R. Voltage = current × resistance." else if lower contains "series" then Bot: "Series total: add them. 10 Ω + 20 Ω = 30 Ω." else if lower contains "parallel" then Bot: "Parallel: 10 Ω + 10 Ω = 5 Ω total." else if lower contains "resistor" and lower contains "colour" then Bot: "Resistor colours: black 0, brown 1, red 2, orange 3, yellow 4." else Bot: [pick random from unknownReplies list from Session 78].

3) Blocks setup — calculator: when ButtonCalcV.Click → if TextBoxI.Text = "" or TextBoxR.Text = "" then set LabelCalc.Text to "Type I and R first" else set global vAnswer to (TextBoxI.Text as number) × (TextBoxR.Text as number) → set LabelCalc.Text to join "V = " + global vAnswer + " V" → set LabelChat.Text to join LabelChat.Text + "\nBot: V = " + global vAnswer + " V".

4) Blocks setup — send/clear: reuse Sessions 77–78 send + clear blocks.

5) Test: ask "What is Ohm's Law?", "series total?", "parallel?", "resistor colour?" — check each answer; type I = 2, R = 10, tap Calculate V → "V = 20 V" and the same answer appears in the chat.

90-minute timing: 0–10 plan/sketch — list 5 electronics questions the bot must answer; 10–20 demo — Rica asks the bot one question; 20–65 build — keyword replies first, calculator second; 65–80 test & fix — ask all 5 questions + test the calculator with 3 values; 80–90 share — Gin asks his bot "What is V when I = 3 and R = 10?" live (answer: 30 V). Test checklist: Each electronics keyword gives the correct fact (check the numbers: series 10 + 20 = 30 Ω, parallel 10 + 10 = 5 Ω). Calculator: 2 × 10 = 20 V; 3 × 10 = 30 V. Common bug: "series" reply fires for the word "series" inside another word, or the calculator joins text instead of multiplying — fix: use contains carefully, and convert TextBox text to numbers before multiplying (check for a 210 instead of 20 — that means text join, not maths). Success check: Gin's bot answers 5 electronics questions correctly and calculates V = I × R. Homework: Add one more question + answer (e.g. "What is power?" → "P = V × I") and one more calculator (e.g. I = V ÷ R). Needs / fallback: Needs no device, account, model or internet — rule-based blocks + maths blocks only. This bot does not "know" electronics — it matches keywords Gin programmed, and Gin must be able to say so.

Session 80Try a pre-made model — Teachable Machine / Lookout (exploration)Wed 24 May 2028
Wed 24 May 2028 | Phase 6 — AI & Smart Apps

Date: Wed 24 May 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can try a pre-made image model (Teachable Machine or Lookout) and describe what it can and cannot recognise, without building his own model. (Exploration.) Components: LabelTitle, Text "Trying a Pre-made Model"; ButtonOpenTeachable, Text "Open Teachable Machine", FontSize 16; ButtonOpenLookout, Text "Open Lookout", FontSize 16; LabelWhat, Text "What did it see?"; TextBoxNotes, Hint "Type what the model guessed, and whether it was right"; ButtonSaveNote, Text "Save Note", FontSize 16; LabelNotesList, Text "Notes:"; WebViewer1, Width Fill parent, Height 300; TinyDB1 (non-visible, tag "premadeModelNotes"). Step-by-step build:

1) Designer setup: add the buttons, labels, TextBox and WebViewer above; set Screen1 Title to "Pre-made Model". Rica decides on the day which tool is used — Teachable Machine (in the browser/WebViewer) or Google Lookout (a separate phone app) — and whether an account is needed. No account is created without Rica, and no model URL is invented in advance.

2) Blocks setup — open: when ButtonOpenTeachable.Click → call WebViewer1.GoToUrl "https://teachablemachine.withgoogle.com/"; when ButtonOpenLookout.Click → set LabelWhat.Text to "Open the Lookout app on the phone (Rica will help) — this app cannot open it by itself".

3) Blocks setup — record results: when ButtonSaveNote.Click → if TextBoxNotes.Text = "" then set LabelWhat.Text to "Type the note first" else set LabelNotesList.Text to join LabelNotesList.Text + "\n• " + TextBoxNotes.Text → call TinyDB1.StoreValue tag "premadeModelNotes" valueToStore LabelNotesList.Text → set TextBoxNotes.Text to "".

4) Blocks setup — load notes: when Screen1.Initialize → set LabelNotesList.Text to call TinyDB1.GetValue tag "premadeModelNotes" valueIfTagNotThere "Notes:".

5) Test (the main work): try the pre-made model on 6 objects (a resistor, a wire, a phone, a hand, a book, a cup) — for each, write in TextBoxNotes: object, what the model guessed, right or wrong. Compare with his own classifier from Sessions 74–76: which was better at resistors, and why (his was trained on resistors; the pre-made one was not).

90-minute timing: 0–10 plan/sketch — list the 6 test objects and predict the model's guesses; 10–20 demo — Rica runs the pre-made model on one object; 20–65 build + test — the notes app first, then test objects 1–3; 65–80 test & fix — test objects 4–6, compare with his own classifier; 80–90 share — Gin reads his notes and says one thing the pre-made model did well and one thing it got wrong. Test checklist: At least 6 objects tested, each with a saved Right/Wrong note. The app's notes survive closing and reopening (TinyDB). Common bug: WebViewer shows a blank Teachable Machine page — fix: check internet, try the phone browser instead of WebViewer, or switch to Lookout; do not invent a model result if the page will not load. Success check: Gin has 6 honest test notes for a pre-made model and can compare it with his own classifier. Homework: Write one sentence: "A pre-made model is good at ___ but bad at ___ because ___." Needs / fallback: Needs internet, a phone/browser that can open Teachable Machine or the Lookout app, and Rica to check any account/sign-in need on the day — no account, model file or model URL is invented here. Fallback: if neither tool opens, test the built-in Personal Image Classifier from Sessions 74–76 on the same 6 objects instead and record the same notes — the comparison skill is the same.

Session 81Smart quiz — quiz that adapts: harder after 3 correctWed 31 May 2028
Wed 31 May 2028 | Phase 6 — AI & Smart Apps

Date: Wed 31 May 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can build a quiz that gets harder after 3 correct answers in a row and easier after a wrong answer. (Exploration — adaptive logic in blocks, not a real AI model.) Components: LabelTitle, Text "Smart Quiz"; LabelLevel, Text "Level: Easy", FontSize 16; LabelQuestion, Text "Tap Start", FontSize 18; ButtonA, Text "A", FontSize 16; ButtonB, Text "B", FontSize 16; ButtonC, Text "C", FontSize 16; ButtonD, Text "D", FontSize 16; LabelScore, Text "Score: 0 | Streak: 0", FontSize 16; LabelFeedback, Text ""; ButtonStart, Text "Start Quiz", FontSize 18; global variables easyQuestions, hardQuestions (lists of question sub-lists, see step 3), score, streak, level (text, "Easy"), currentQ (number, 1). Step-by-step build:

1) Designer setup: add the labels, four answer buttons and Start button above; set Screen1 Title to "Smart Quiz".

2) Blocks setup — question lists: initialize global easyQuestions to create empty list with 3 easy items, each a sub-list [question, A, B, C, D, correct letter] — e.g. ["What is V when I = 2 A and R = 10 Ω?", "5 V", "10 V", "20 V", "40 V", "C"]; initialize global hardQuestions with 3 harder items — e.g. ["Two resistors in parallel, 10 Ω and 10 Ω. Total?", "5 Ω", "10 Ω", "20 Ω", "0 Ω", "A"] and ["P = V × I. V = 10 V, I = 2 A. P = ?", "5 W", "12 W", "20 W", "200 W", "C"].

3) Blocks setup — show: procedure showQuestion → set local listToUse to if global level = "Easy" then global easyQuestions else global hardQuestions → set local q to select list item listToUse global currentQ → set LabelQuestion.Text to item 1 of local q → set ButtonA.Text to item 2, ButtonB.Text to item 3, ButtonC.Text to item 4, ButtonD.Text to item 5.

4) Blocks setup — answer + adapt: procedure checkAnswer letter → set local q to [current question as in step 3] → if letter = item 6 of local q then set global score to global score + 1 → set global streak to global streak + 1 → set LabelFeedback.Text to "Correct!" → if global streak >= 3 and global level = "Easy" then set global level to "Hard" → set LabelLevel.Text to "Level: Hard" → set global streak to 0 → set LabelFeedback.Text to join LabelFeedback.Text + " Level up — harder questions now!" else set global streak to 0 → set global level to "Easy" → set LabelLevel.Text to "Level: Easy" → set LabelFeedback.Text to "Not quite — back to Easy." → set LabelScore.Text to join "Score: " + global score + " | Streak: " + global streak → set global currentQ to global currentQ + 1 → if global currentQ > length of list [current list] then set global currentQ to 1 → call procedure showQuestion.

5) Blocks setup — start: when ButtonStart.Click → set global score to 0 → set global streak to 0 → set global level to "Easy" → set global currentQ to 1 → set LabelLevel.Text to "Level: Easy" → call procedure showQuestion; wire ButtonA–D to call checkAnswer "A" etc.

6) Test: answer 3 easy questions correctly → level must change to Hard; answer one hard question wrong → level drops back to Easy.

90-minute timing: 0–10 plan/sketch — write 3 easy + 3 hard questions on paper; 10–20 demo — Rica plays a quiz that levels up; 20–65 build — lists + show first, adapt logic second; 65–80 test & fix — play two full rounds (one all-correct, one with a wrong answer); 80–90 share — Gin plays one round for Rica and explains the 3-in-a-row rule. Test checklist: 3 correct in a row → "Level: Hard" and harder questions appear. A wrong answer → back to "Level: Easy". Score and streak update every answer. Common bug: level never changes — fix: check the if global streak >= 3 block is inside the correct-answer branch (not the wrong branch), and that streak resets to 0 on level-up. Success check: Gin's quiz changes difficulty by itself based on his streak. Homework: Write 3 more hard questions (with answers) to add to the hard list. Needs / fallback: Needs no device, account, model or internet — lists + if/else blocks only. If time is short, use 2 questions per level instead of 3 (keep the 3-correct rule, with the list wrapping round).

Session 82Recommendation app — answer 3 questions, app suggests a projectWed 7 Jun 2028
Wed 7 Jun 2028 | Phase 6 — AI & Smart Apps

Date: Wed 7 Jun 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can build an app that asks 3 questions and recommends a project based on the answers, using scores in blocks. (Exploration — rule-based scoring, not a real AI model.) Components: LabelTitle, Text "What Should I Build?"; LabelQ1, Text "1. Do you like games or tools?"; ButtonQ1Games, Text "Games", FontSize 16; ButtonQ1Tools, Text "Tools", FontSize 16; LabelQ2, Text "2. Do you like sensors or maths?"; ButtonQ2Sensors, Text "Sensors", FontSize 16; ButtonQ2Maths, Text "Maths", FontSize 16; LabelQ3, Text "3. Solo or with a friend?"; ButtonQ3Solo, Text "Solo", FontSize 16; ButtonQ3Friend, Text "With a friend", FontSize 16; ButtonRecommend, Text "Recommend a Project!", FontSize 18; LabelResult, Text "Answer all 3 questions first", FontSize 18; global variables gameScore, toolScore, sensorScore, mathsScore (numbers, 0), q1Done, q2Done, q3Done (booleans, false). Step-by-step build:

1) Designer setup: add the three question labels with their two answer buttons each, the Recommend button and LabelResult; set Screen1 Title to "Project Recommender".

2) Blocks setup — score the answers: when ButtonQ1Games.Click → set global gameScore to global gameScore + 2 → set global q1Done to true → set LabelQ1.Text to "1. Games ✓"; when ButtonQ1Tools.Click → set global toolScore to global toolScore + 2 → set global q1Done to true → set LabelQ1.Text to "1. Tools ✓". Same pattern for Q2 (Sensors → sensorScore +2; Maths → mathsScore +2) and Q3 (Solo → no score change, just q3Done = true; Friend → no score change — or +1 to gameScore, Gin's choice, written down).

3) Blocks setup — recommend: when ButtonRecommend.Click → if not global q1Done or not global q2Done or not global q3Done then set LabelResult.Text to "Answer all 3 questions first" else if global gameScore >= global toolScore and global sensorScore >= global mathsScore then set LabelResult.Text to "Try: a tilt maze game (sensors + games)!" else if global gameScore >= global toolScore then set LabelResult.Text to "Try: a reaction game with maths scoring!" else if global sensorScore >= global mathsScore then set LabelResult.Text to "Try: a sensor measurement logger!" else set LabelResult.Text to "Try: a series/parallel circuit calculator!".

4) Blocks setup — reset: add ButtonAgain, Text "Start Again"; when ButtonAgain.Click → set all four scores to 0 → set q1Done/q2Done/q3Done to false → reset the three question labels → set LabelResult.Text to "Answer all 3 questions first".

5) Test: answer Games + Sensors + Solo → maze game recommendation; answer Tools + Maths + Solo → circuit calculator; tap Recommend with a question unanswered → warning, not a recommendation.

90-minute timing: 0–10 plan/sketch — list 4 possible recommendations and which answers lead to each; 10–20 demo — Rica answers and gets a recommendation; 20–65 build — scoring first, recommend logic second; 65–80 test & fix — try all 4 answer combinations; 80–90 share — Gin answers as Ray would, and reads the recommendation the app gives. Test checklist: All 4 combinations give the intended recommendation. Unanswered question → warning. Start Again resets everything. Common bug: the same recommendation appears for every combination — fix: check the scores actually increase in step 2 (tap a button and watch the score — add a temporary label showing the scores to debug, then remove it). Success check: Gin's app recommends a sensible project from 3 answers, with different answers giving different recommendations. Homework: Add a 4th question (e.g. "Inside or outside?") and a 5th recommendation of his own. Needs / fallback: Needs no device, account, model or internet — scoring + if/else blocks only. The "recommendation" is Gin's own rules, and he must be able to say so — it is not the app understanding him.

Session 83Voice assistant logic — speak a command, app respondsWed 14 Jun 2028
Wed 14 Jun 2028 | Phase 6 — AI & Smart Apps

Date: Wed 14 Jun 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can build a voice assistant: speak a command, the app shows the words it heard, and replies with text-to-speech. (Exploration.) Components: LabelTitle, Text "Voice Assistant"; ButtonListen, Text "🎤 Listen", FontSize 18; LabelHeard, Text "I heard: —", FontSize 16; LabelReply, Text "Reply: —", FontSize 16; ButtonSpeakReply, Text "Speak the Reply", FontSize 16; SpeechRecognizer1 (non-visible); TextToSpeech1 (non-visible). Step-by-step build:

1) Designer setup: add the labels and buttons above; set Screen1 Title to "Voice Assistant"; drag in SpeechRecognizer1 and TextToSpeech1.

2) Blocks setup — listen: when ButtonListen.Click → call SpeechRecognizer1.GetText and set LabelHeard.Text to "Listening…".

3) Blocks setup — heard: when SpeechRecognizer1.AfterGettingText result → set LabelHeard.Text to join "I heard: " + result → call procedure reply result.

4) Blocks setup — reply (reuse Session 79 keywords): procedure reply heardText → set local lower to [heardText in lower case] → if lower contains "ohm" then set LabelReply.Text to "Reply: Ohm's Law is V equals I times R." else if lower contains "hello" then set LabelReply.Text to "Reply: Hello! How can I help?" else if lower contains "time" then set LabelReply.Text to join "Reply: I cannot tell the time yet — try asking about Ohm's Law." else set LabelReply.Text to "Reply: I did not understand that. Try Ohm's Law or hello.".

5) Blocks setup — speak: when ButtonSpeakReply.Click → if LabelReply.Text = "Reply: —" then set LabelReply.Text to "Reply: Ask me something first!" else call TextToSpeech1.Speak [LabelReply.Text without the "Reply: " prefix — use the replace text block or store the reply text in a global variable replyText]; add when SpeechRecognizer1.AfterGettingText also calls the speak step automatically if Gin prefers — choose one, not both, and write the choice down.

6) Test: tap Listen, say "hello" clearly, check LabelHeard shows "hello" and the reply appears; say "Ohm's Law"; say a nonsense word and check the honest reply.

90-minute timing: 0–10 plan/sketch — list 4 voice commands and their replies; 10–20 demo — Rica speaks one command live; 20–65 build — listen + heard first, reply second, speak third; 65–80 test & fix — test each command twice, in a quiet spot; 80–90 share — Gin speaks a command and the phone answers him out loud. Test checklist: Spoken "hello" → heard text shows "hello" → correct reply appears → Speak reads it aloud. Unclear speech → honest "did not understand" reply, not a made-up answer. Common bug: recognizer hears nothing or the wrong word — fix: speak slowly in a quiet room, hold the phone close, and check microphone permission; if it keeps mishearing, type the command in a TextBox as a backup input (same reply procedure). Success check: Gin speaks a command, the app shows what it heard, replies, and speaks the reply. Homework: Add 2 new voice commands + replies (e.g. "resistor" and "thank you"). Needs / fallback: Needs a phone microphone, SpeechRecognizer + TextToSpeech (both need internet on most Android phones for recognition — Rica checks on the day). Fallback: if speech recognition will not work, use a TextBox to type the command and keep the same reply + TextToSpeech steps — the assistant logic is identical, only the input changes.

Session 84AI + sensor — classifier + accelerometer triggerWed 21 Jun 2028
Wed 21 Jun 2028 | Phase 6 — AI & Smart Apps

Date: Wed 21 Jun 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can combine his image classifier with the accelerometer: the app only classifies a photo when the phone is shaken or tilted. (Exploration.) Components: LabelTitle, Text "Shake to Classify"; ImagePreview, Picture "", Width 250, Height 200; ButtonTakePhoto, Text "Take Photo", FontSize 18; LabelShake, Text "Shake the phone to classify!", FontSize 16; LabelResult, Text "Result: —", FontSize 18; LabelAccel, Text "X: 0 Y: 0 Z: 0", FontSize 14; AccelerometerSensor1 (non-visible, Enabled true); Camera1; PersonalImageClassifier1; global variables lastImage (text, ""), alreadyClassified (boolean, false). Step-by-step build:

1) Designer setup: add the Image, buttons and labels above; set Screen1 Title to "Shake to Classify"; load the trained 3-class model from Sessions 74–76 (Rica helps).

2) Blocks setup — photo: when ButtonTakePhoto.Click → call Camera1.TakePicture; when Camera1.AfterPicture image → set ImagePreview.Picture to image → set global lastImage to image → set global alreadyClassified to false → set LabelResult.Text to "Photo ready — now shake!".

3) Blocks setup — shake trigger: when AccelerometerSensor1.AccelerationChanged xAccel yAccel zAccel → set LabelAccel.Text to join "X: " + xAccel + " Y: " + yAccel + " Z: " + zAccel → if absolute value of xAccel > 12 or absolute value of yAccel > 12 then [if global lastImage ≠ "" and not global alreadyClassified then set global alreadyClassified to true → set LabelShake.Text to "Shaken! Classifying…" → call PersonalImageClassifier1.Classify global lastImage].

4) Blocks setup — result: when PersonalImageClassifier1.ClassificationComplete result → set LabelResult.Text to join "Result: " + result → set LabelShake.Text to "Shake again for the next photo".

5) Test: take a photo of a resistor, shake the phone firmly once → result appears; take a photo and do not shake → no result (the trigger matters); shake with no photo → nothing happens (no crash).

90-minute timing: 0–10 plan/sketch — draw the flow: photo → shake → result; 10–20 demo — Rica shakes and a result appears; 20–65 build — photo first, shake trigger second, result third; 65–80 test & fix — classify 4 objects by shaking, tune the shake threshold (12) up/down if it triggers too easily or never; 80–90 share — Gin demos shake-to-classify to Rica with a resistor photo. Test checklist: Shake with a photo → classification runs once. No shake → no classification. Shake with no photo → no crash. Common bug: the classifier runs many times per shake — fix: the alreadyClassified flag in step 3 (set true before classifying, reset false on a new photo); also raise the threshold from 12 to 15 if normal walking triggers it. Success check: Gin's app classifies only after a shake, and shows the result. Homework: Change the trigger to a tilt (e.g. tilt phone left, xAccel < −5) and test whether it still works. Needs / fallback: Needs the trained classifier model, a camera, and an accelerometer (most phones have one — check with the live X/Y/Z display). Fallback: if the classifier model will not load, replace Classify with the rule-based guesser from Session 73 and keep the shake trigger — the sensor + trigger logic is still learned. If the phone has no accelerometer, use a Button "Classify" as the trigger instead and note the swap.

Session 85AI + TinyDB — save classifier results, view historyWed 28 Jun 2028
Wed 28 Jun 2028 | Phase 6 — AI & Smart Apps

Date: Wed 28 Jun 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can save every classifier result to TinyDB with the date/time, and view the saved history in a list. (Exploration.) Components: LabelTitle, Text "Classifier History"; ImagePreview, Picture "", Width 200, Height 150; ButtonTakePhoto, Text "Take Photo", FontSize 16; ButtonClassify, Text "Classify & Save", FontSize 18; LabelResult, Text "Result: —", FontSize 18; ListViewHistory, ElementsFromString ""; ButtonClearHistory, Text "Clear History", FontSize 16; LabelCount, Text "Saved: 0"; Camera1; PersonalImageClassifier1; TinyDB1 (non-visible); Clock1 (non-visible, for the time); global variables lastImage (text, ""), historyList (empty list). Step-by-step build:

1) Designer setup: add the Image, buttons, labels and ListView above; set Screen1 Title to "Classifier History"; load the trained model from Sessions 74–76.

2) Blocks setup — load history: when Screen1.Initialize → set global historyList to call TinyDB1.GetValue tag "classifierHistory" valueIfTagNotThere create empty list → set ListViewHistory.Elements to global historyList → set LabelCount.Text to join "Saved: " + length of list global historyList.

3) Blocks setup — classify + save: when ButtonTakePhoto.Click → call Camera1.TakePicture; when Camera1.AfterPicture image → set ImagePreview.Picture to image → set global lastImage to image; when ButtonClassify.Click → if global lastImage = "" then set LabelResult.Text to "Take a photo first" else call PersonalImageClassifier1.Classify global lastImage.

4) Blocks setup — on result: when PersonalImageClassifier1.ClassificationComplete result → set LabelResult.Text to join "Result: " + result → set local entry to join call Clock1.Now + " — " + result → add items to list global historyList item local entry → set ListViewHistory.Elements to global historyList → call TinyDB1.StoreValue tag "classifierHistory" valueToStore global historyList → set LabelCount.Text to join "Saved: " + length of list global historyList.

5) Blocks setup — clear: when ButtonClearHistory.Click → set global historyList to create empty list → set ListViewHistory.Elements to global historyList → call TinyDB1.ClearTag tag "classifierHistory" → set LabelCount.Text to "Saved: 0". Note: Clear only clears this tag — it does not wipe other apps' data.

6) Test: classify 3 objects, close the app fully, reopen it — the history must still be there; tap Clear History and check it empties.

90-minute timing: 0–10 plan/sketch — draw the history list and what each entry shows (time + result); 10–20 demo — Rica shows a saved list surviving a restart; 20–65 build — classify first, save second, load-on-open third; 65–80 test & fix — classify 5 objects, restart, check history; 80–90 share — Gin shows Rica his saved history and reads the oldest entry. Test checklist: Classify → entry appears in the list with a time. Close + reopen → history is still there. Clear → list empties and count shows 0. Common bug: history disappears after reopening — fix: check step 2 loads from TinyDB on Initialize with the exact tag "classifierHistory", and that step 4 stores the whole list (not just the latest entry). Success check: Gin's classifier history survives closing and reopening the app. Homework: Classify 3 more objects at home and check they are in the history tomorrow. Needs / fallback: Needs the trained classifier model and a camera. Fallback: if the model will not load, save manual entries instead — a TextBox + Button "Save Guess" that stores typed guesses with the time, using the same TinyDB list — the storage logic is identical.

Session 86AI ethics & limits — when the classifier is wrong, why? (discussion + test)Wed 5 Jul 2028
Wed 5 Jul 2028 | Phase 6 — AI & Smart Apps

Date: Wed 5 Jul 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can test his classifier on tricky photos, explain why it got some wrong (bad training data, similar objects, poor light), and say when not to trust it. (Exploration — discussion + test, no new model.) Components: LabelTitle, Text "When Is the Classifier Wrong?"; LabelQuestion, Text "Test photo: —"; ImageTest, Picture "", Width 250, Height 200; ButtonTestA, Text "Test: Resistor in the Dark", FontSize 16; ButtonTestB, Text "Test: Wire Next to Resistor", FontSize 16; ButtonTestC, Text "Test: Blurry Photo", FontSize 16; LabelGuess, Text "Guess: —", FontSize 16; LabelRightWrong, Text "Was it right?"; ButtonRight, Text "✓ Right", FontSize 16; ButtonWrong, Text "✗ Wrong", FontSize 16; LabelWhy, Text "Why it went wrong:"; TextBoxWhy, Hint "e.g. too dark, looks like a wire"; ButtonSaveWhy, Text "Save Reason", FontSize 16; Camera1; PersonalImageClassifier1; TinyDB1 (tag "classifierMistakes"); global variables correct, wrong (numbers, 0). Step-by-step build:

1) Designer setup: add the labels, Image, three test buttons, Right/Wrong buttons, TextBoxWhy and Save button; set Screen1 Title to "AI Limits"; load the trained model from Sessions 74–76.

2) Blocks setup — tricky tests: when ButtonTestA.Click → set LabelQuestion.Text to "Test photo: resistor in the dark — take the photo now" → call Camera1.TakePicture; same for TestB ("wire next to a resistor") and TestC ("blurry photo — move the phone while taking it"). when Camera1.AfterPicture image → set ImageTest.Picture to image → call PersonalImageClassifier1.Classify image.

3) Blocks setup — result + count: when PersonalImageClassifier1.ClassificationComplete result → set LabelGuess.Text to join "Guess: " + result → set LabelRightWrong.Text to "Was it right? Tap ✓ or ✗"; when ButtonRight.Click → set global correct to global correct + 1 → set LabelRightWrong.Text to join "Right: " + global correct + " | Wrong: " + global wrong; when ButtonWrong.Click → set global wrong to global wrong + 1 → [same update] → set LabelWhy.Text to "Why? Type a reason and tap Save Reason".

4) Blocks setup — save the reason: when ButtonSaveWhy.Click → if TextBoxWhy.Text = "" then set LabelWhy.Text to "Type a reason first" else call TinyDB1.StoreValue tag "classifierMistakes" valueToStore join [old value + "\n• " + LabelGuess.Text + " — " + TextBoxWhy.Text] → set TextBoxWhy.Text to "" → set LabelWhy.Text to "Saved. Try the next tricky photo.".

5) Test + discuss (the main work): run all three tricky tests, count Right/Wrong, and for each Wrong write a reason — then discuss with Rica: (a) the classifier only knows what it was trained on; (b) dark/blurry/similar objects confuse it; (c) never trust it for safety, money, or identifying a person — a wrong resistor guess is harmless, a wrong medical/safety guess is not.

90-minute timing: 0–10 plan/sketch — predict which tricky photo will fool it most; 10–20 demo/discussion — Rica shows one wrong guess and asks why; 20–65 build + test — the test buttons first, then all three tricky photos; 65–80 test & fix — count Right/Wrong, save a reason for every Wrong; 80–90 share — Gin presents his Right/Wrong count and his best explanation of why the classifier failed. Test checklist: All three tricky photos tested with a Right/Wrong tap and a saved reason for each Wrong. The app never claims a guess is certain — it shows a guess, and Gin judges it. Common bug: Gin marks a wrong guess as Right because he wants a good score — fix: Rica checks one photo herself; the honest count matters more than a high count, and a low score here is a good finding. Success check: Gin can explain, with his own test evidence, two reasons a classifier goes wrong and one situation where it must not be trusted. Homework: Find one more tricky photo at home (e.g. an object half-hidden) and test it. Needs / fallback: Needs the trained model and a camera. Fallback: if the model will not load, run the same three tricky tests on the pre-made model from Session 80 (or the rule-based guesser) and record the same Right/Wrong + reason — the lesson is about limits, not about which model fails.

Session 87Smart app 1: resistor identifier — photo / classifier + decoder combinedWed 12 Jul 2028
Wed 12 Jul 2028 | Phase 6 — AI & Smart Apps

Date: Wed 12 Jul 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can combine his classifier (photo → "resistor") with his colour-code decoder (colours → value) in one resistor identifier app. (Exploration.) Components: LabelTitle, Text "Resistor Identifier"; ImagePhoto, Picture "", Width 250, Height 180; ButtonTakePhoto, Text "Take Photo", FontSize 18; ButtonIdentify, Text "Identify", FontSize 18; LabelClassifier, Text "Classifier says: —", FontSize 16; LabelBand1, Text "Band 1:"; SpinnerBand1, ElementsFromString "Black, Brown, Red, Orange, Yellow, Green, Blue, Violet, Grey, White"; LabelBand2, Text "Band 2:"; SpinnerBand2 (same colour list); LabelBand3, Text "Band 3 (multiplier):"; SpinnerBand3 (same colour list); ButtonDecode, Text "Decode Value", FontSize 18; LabelValue, Text "Value: —", FontSize 20; Camera1; PersonalImageClassifier1; global variable lastImage (text, ""). Step-by-step build:

1) Designer setup: add the Image, photo/identify buttons, classifier label, three colour Spinners with their labels, Decode button and value label; set Screen1 Title to "Resistor Identifier". (Colour values from Session 4 / his 6 Nov 2026 report: black 0, brown 1, red 2, orange 3, yellow 4, green 5, blue 6, violet 7, grey 8, white 9.)

2) Blocks setup — photo + classify: when ButtonTakePhoto.Click → call Camera1.TakePicture; when Camera1.AfterPicture image → set ImagePhoto.Picture to image → set global lastImage to image; when ButtonIdentify.Click → if global lastImage = "" then set LabelClassifier.Text to "Take a photo first" else call PersonalImageClassifier1.Classify global lastImage; when PersonalImageClassifier1.ClassificationComplete result → set LabelClassifier.Text to join "Classifier says: " + result → if result ≠ "Resistor" then set LabelClassifier.Text to join LabelClassifier.Text + " — check it really is a resistor before decoding!".

3) Blocks setup — decode (from Session 4): when ButtonDecode.Click → set local d1 to [index of SpinnerBand1.Selection in the colour list minus 1] → set local d2 to [same for SpinnerBand2] → set local mult to [10 to the power of (index of SpinnerBand3.Selection minus 1)] → set local value to (d1 × 10 + d2) × mult → set LabelValue.Text to join "Value: " + local value + " Ω". Example: brown (1), black (0), red (×100) → (10 + 0) × 100 = 1,000 Ω.

4) Test: photograph a real resistor, tap Identify (expect "Resistor"), set the Spinners to its real bands, tap Decode, and check the value against the resistor's known value (or Rica's check).

90-minute timing: 0–10 plan/sketch — draw the two halves: photo half + decoder half; 10–20 demo — Rica identifies one resistor end to end; 20–65 build — classify half first, decoder half second; 65–80 test & fix — test 3 real resistors, compare decoded values; 80–90 share — Gin identifies one resistor for Rica, photo to value. Test checklist: Photo → classifier says "Resistor" (or warns if not). Spinners set to brown/black/red → "Value: 1000 Ω". Wrong bands → a wrong value, honestly shown (the decoder trusts Gin's band reading). Common bug: multiplier wrong by ×10 — fix: check the power: red as multiplier is ×100 (10²), not ×10; test with brown/black/red = 1,000 Ω and brown/black/brown = 100 Ω. Success check: Gin identifies a real resistor by photo and decodes its value in one app. Homework: Identify 3 resistors at home (photo + bands + decoded value) and write the values down. Needs / fallback: Needs the trained classifier model, a camera, and real resistors to photograph. Fallback: if the classifier will not load, skip the Identify step and use the decoder half only, with a label "Classifier not available today — decoder only" — do not invent a classifier result. The decoder half alone still counts as the session's core skill.

Session 88Smart app 2: circuit helper — chatbot + calculator combinedWed 19 Jul 2028
Wed 19 Jul 2028 | Phase 6 — AI & Smart Apps

Date: Wed 19 Jul 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can combine his electronics chatbot (Session 79) with his circuit calculators (Sessions 91–92 logic, built here in simple form) in one circuit helper app. (Exploration.) Components: LabelTitle, Text "Circuit Helper"; LabelChat, Text "Bot: Ask me about circuits!", FontSize 16, Height 200; TextBoxAsk, Hint "e.g. series total?"; ButtonSend, Text "Send", FontSize 16; TextBoxR1, Hint "Resistor 1 (Ω), e.g. 10"; TextBoxR2, Hint "Resistor 2 (Ω), e.g. 20"; ButtonSeries, Text "Series Total", FontSize 16; ButtonParallel, Text "Parallel Total", FontSize 16; LabelCalc, Text "Total: —", FontSize 18; TextBoxV, Hint "Voltage V"; TextBoxR, Hint "Total R (Ω)"; ButtonCurrent, Text "Current I = V ÷ R", FontSize 16; LabelCurrent, Text "Current: —", FontSize 16. Step-by-step build:

1) Designer setup: add the chat labels/buttons at the top, then the R1/R2 TextBoxes with Series/Parallel buttons and LabelCalc, then the V/R TextBoxes with the Current button and LabelCurrent; set Screen1 Title to "Circuit Helper".

2) Blocks setup — chatbot: reuse Session 79 procedure reply — keywords "ohm", "series" ("Series total: add them. 10 Ω + 20 Ω = 30 Ω."), "parallel" ("Parallel: 10 Ω + 10 Ω = 5 Ω total."), "power" ("P = V × I"), plus unknown → random honest reply from the Session 78 list. Wire when ButtonSend.Click as in Session 77.

3) Blocks setup — series: when ButtonSeries.Click → if TextBoxR1.Text = "" or TextBoxR2.Text = "" then set LabelCalc.Text to "Type both resistors first" else set LabelCalc.Text to join "Series total: " + ((TextBoxR1.Text as number) + (TextBoxR2.Text as number)) + " Ω" — check: 10 + 20 = 30 Ω.

4) Blocks setup — parallel: when ButtonParallel.Click → [same empty check] else set local r1 to TextBoxR1.Text as number → set local r2 to TextBoxR2.Text as number → set local total to 1 ÷ ((1 ÷ local r1) + (1 ÷ local r2)) → set LabelCalc.Text to join "Parallel total: " + local total + " Ω" — check: 10 and 10 → 5 Ω; 10 and 20 → 6.67 Ω (round to 2 decimal places with the format block if shown).

5) Blocks setup — current: when ButtonCurrent.Click → if TextBoxV.Text = "" or TextBoxR.Text = "" then set LabelCurrent.Text to "Type V and R first" else set LabelCurrent.Text to join "Current: " + ((TextBoxV.Text as number) ÷ (TextBoxR.Text as number)) + " A" — check: V = 20, R = 10 → 2 A. Also copy the total into TextBoxR automatically after a Series/Parallel tap, so Gin does not retype it.

6) Test: ask the bot "series total?", then tap Series Total with 10 + 20 → 30 Ω; tap Parallel with 10 + 10 → 5 Ω; calculate current with V = 20, R = 10 → 2 A.

90-minute timing: 0–10 plan/sketch — draw the chat half and calculator half; 10–20 demo — Rica asks the bot then calculates a total; 20–65 build — chatbot first, series/parallel second, current third; 65–80 test & fix — test all three calculations with two sets of values each; 80–90 share — Gin demos the full helper: one bot question + one series + one parallel calculation. Test checklist: Bot answers series/parallel/power correctly. Series 10 + 20 = 30 Ω; parallel 10 + 10 = 5 Ω; current 20 ÷ 10 = 2 A. Common bug: parallel gives 0.2 or 20 instead of 5 — fix: check the brackets — it must be 1 ÷ ((1 ÷ R1) + (1 ÷ R2)), not (1 ÷ R1) + (1 ÷ R2) alone; and check text was converted to numbers. Success check: Gin's helper answers a circuit question and calculates series, parallel and current correctly. Homework: Use the helper to solve: R1 = 20 Ω, R2 = 20 Ω in parallel, V = 10 V — what is the total and the current? (Answers: 10 Ω, 1 A.) Needs / fallback: Needs no device, account, model or internet — chatbot rules + maths blocks only. If time is short, build series + current and leave parallel as homework (its formula is practised again in Session 92).

Session 89AI showcase — demo best AI app, fix wrong answersWed 26 Jul 2028
Wed 26 Jul 2028 | Phase 6 — AI & Smart Apps

Date: Wed 26 Jul 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can demo his best AI app (Sessions 73–88), find its wrong answers live, and fix at least two of them. (Exploration.) Components: LabelTitle, Text "AI Showcase"; ListViewAIApps, ElementsFromString "Classifier App, Electronics Helper Bot, Smart Quiz, Recommendation App, Voice Assistant, Resistor Identifier, Circuit Helper, Classifier History"; LabelDemo, Text "Demo app: —", FontSize 16; LabelWrongList, Text "Wrong answers found:"; TextBoxWrong, Hint "Type a wrong answer, e.g. Bot said parallel 10+10=20"; ButtonAddWrong, Text "Log Wrong Answer", FontSize 16; ButtonFixed, Text "Mark Fixed", FontSize 16; LabelBest, Text "My best AI app: —"; TinyDB1 (tag "aiShowcaseWrongs"). Step-by-step build:

1) Designer setup: add the ListView of AI apps, the wrong-answer log (TextBox + buttons + label), and the best-app label; set Screen1 Title to "AI Showcase".

2) Blocks setup — log wrongs: when ButtonAddWrong.Click → if TextBoxWrong.Text = "" then set LabelWrongList.Text to "Type the wrong answer first" else set LabelWrongList.Text to join LabelWrongList.Text + "\n• " + TextBoxWrong.Text → call TinyDB1.StoreValue tag "aiShowcaseWrongs" valueToStore LabelWrongList.Text → set TextBoxWrong.Text to "".

3) Blocks setup — load + pick best: when Screen1.Initialize → set LabelWrongList.Text to call TinyDB1.GetValue tag "aiShowcaseWrongs" valueIfTagNotThere "Wrong answers found:"; when ListViewAIApps.AfterPicking → set LabelDemo.Text to join "Demo app: " + ListViewAIApps.Selection → set LabelBest.Text to join "My best AI app: " + ListViewAIApps.Selection.

4) Test + fix (the main work): demo each AI app to Rica (and Ray/Run if they watch), deliberately try inputs that broke it before — a tricky classifier photo, a chatbot keyword it does not know, a parallel calculation — log every wrong answer, then fix the top 2 in the original apps (e.g. add the missing chatbot keyword, correct the parallel formula brackets from Session 88, add more training photos for a confused class) and re-test.

5) Finish: Gin names his best AI app in LabelBest and says why — most useful, most correct, or most fun — and what he would still not trust it to do (Session 86).

90-minute timing: 0–10 plan/sketch — list the 8 AI apps and the order to demo them; 10–20 demo — Rica demos one app and logs one wrong answer; 20–65 build + demo — demo apps in order, log wrongs; 65–80 test & fix — fix the top 2 wrongs, re-test; 80–90 share — Gin presents his best AI app and reads his wrong-answer list. Test checklist: Every AI app demoed at least once; every wrong answer logged before fixing; top 2 wrongs fixed and re-tested. Common bug: a "fix" that only hides the wrong answer (e.g. deleting the question) — fix: the fix must make the right answer appear (add the keyword, correct the formula, retrain) — hiding it does not count. Success check: Gin has a saved wrong-answer list, 2 fixes verified, and a named best AI app with a reason. Homework: Back up all Phase 6 project files (.aia) with Rica. Needs / fallback: Needs Gin's Phase 6 apps and (for the classifier apps) the trained model + camera. Fallback: any app that cannot run live is demoed from its Blocks/screenshots and marked "not tested live today" — do not invent a demo result.

Session 90AI review — what worked, what was unreliable, what to keepWed 2 Aug 2028
Wed 2 Aug 2028 | Phase 6 — AI & Smart Apps

Date: Wed 2 Aug 2028 | Phase: Phase 6 — AI & Smart Apps Learning objective: Gin can review Phase 6 honestly: sort his AI apps into worked / unreliable / keep, and say what he learned about AI. (Exploration.) Components: LabelTitle, Text "AI Review"; ListViewAIApps, ElementsFromString "Classifier App, Electronics Helper Bot, Smart Quiz, Recommendation App, Voice Assistant, Resistor Identifier, Circuit Helper, Classifier History"; ButtonWorked, Text "✓ Worked", FontSize 16; ButtonUnreliable, Text "⚠ Unreliable", FontSize 16; ButtonKeep, Text "★ Keep", FontSize 16; LabelReview, Text "Worked:\nUnreliable:\nKeep:"; LabelLearned, Text "What I learned about AI:"; TextBoxLearned, Hint "e.g. A classifier is only as good as its training photos"; ButtonSaveLearned, Text "Save", FontSize 16; TinyDB1 (tags "aiReview", "aiLearned"). Step-by-step build:

1) Designer setup: add the ListView, three verdict buttons, the review label, and the learned TextBox + Save button; set Screen1 Title to "AI Review".

2) Blocks setup — verdicts: when ButtonWorked.Click → if ListViewAIApps.Selection = "" then set LabelReview.Text to "Pick an app first" else set LabelReview.Text to [LabelReview.Text with the app name added under "Worked:"] → call TinyDB1.StoreValue tag "aiReview" valueToStore LabelReview.Text. Same pattern for ButtonUnreliable ("Unreliable:") and ButtonKeep ("Keep:") — an app can be in more than one list (e.g. Worked and Keep, or Unreliable but Keep to fix later).

3) Blocks setup — learned: when ButtonSaveLearned.Click → if TextBoxLearned.Text = "" then set LabelLearned.Text to "Type what you learned first" else set LabelLearned.Text to join "What I learned about AI: " + TextBoxLearned.Text → call TinyDB1.StoreValue tag "aiLearned" valueToStore TextBoxLearned.Text → set TextBoxLearned.Text to "".

4) Blocks setup — load: when Screen1.Initialize → set LabelReview.Text to call TinyDB1.GetValue tag "aiReview" valueIfTagNotThere "Worked:\nUnreliable:\nKeep:" → set LabelLearned.Text to join "What I learned about AI: " + call TinyDB1.GetValue tag "aiLearned" valueIfTagNotThere "".

5) Review (the main work): go through each Phase 6 app with Rica, using the evidence from Sessions 75 (accuracy count), 86 (Right/Wrong + reasons) and 89 (wrong-answer list) — not memory or wishes — and give it a verdict. Finish by writing one learned sentence each for: classifiers, chatbots, and "when not to trust AI".

90-minute timing: 0–10 plan/sketch — list the 8 apps and what evidence exists for each; 10–20 demo — Rica reviews one app from its evidence; 20–65 build + review — verdicts for apps 1–4; 65–80 test & fix — verdicts for apps 5–8, write the learned sentences; 80–90 share — Gin reads his full review and his three learned sentences to Rica. Test checklist: Every Phase 6 app has at least one verdict; the review is saved in TinyDB and survives reopening; the learned sentences mention training data (classifiers), keywords (chatbots), and a not-to-trust case. Common bug: verdicts disappear on reopen — fix: check the tag names match exactly ("aiReview", "aiLearned") in both the save and load blocks. Success check: Gin produces a saved, evidence-based review of all Phase 6 AI apps plus three learned sentences. Homework: Choose one "Keep" app to polish in Phase 7, and write what the polish would be. Needs / fallback: Needs Gin's Phase 6 evidence (accuracy counts, wrong-answer lists) — if a count was never recorded, mark that app "Unreliable — no evidence" rather than guessing a verdict. No device, account, model or internet is needed for the review itself.

Session 91Series circuit calculator — total resistance, current, voltage dropWed 9 Aug 2028
Wed 9 Aug 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 9 Aug 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a series circuit calculator that gives total resistance, current, and each resistor's voltage drop from V, R1 and R2. Components: LabelTitle, Text "Series Circuit Calculator"; TextBoxV, Hint "Supply voltage V, e.g. 20"; TextBoxR1, Hint "Resistor 1 (Ω), e.g. 10"; TextBoxR2, Hint "Resistor 2 (Ω), e.g. 20"; ButtonCalc, Text "Calculate Series Circuit", FontSize 18; LabelTotal, Text "Total R: —", FontSize 16; LabelCurrent, Text "Current I: —", FontSize 16; LabelDrop1, Text "Voltage drop R1: —", FontSize 16; LabelDrop2, Text "Voltage drop R2: —", FontSize 16; LabelCheck, Text "Check: drops add up to V"; ButtonClear, Text "Clear", FontSize 16. Step-by-step build:

1) Designer setup: add the three TextBoxes, Calculate/Clear buttons and four result labels above; set Screen1 Title to "Series Calculator".

2) Blocks setup — calculate: when ButtonCalc.Click → if TextBoxV.Text = "" or TextBoxR1.Text = "" or TextBoxR2.Text = "" then set LabelTotal.Text to "Type V, R1 and R2 first" else set local totalR to (TextBoxR1.Text as number) + (TextBoxR2.Text as number) → set local current to (TextBoxV.Text as number) ÷ local totalR → set LabelTotal.Text to join "Total R: " + local totalR + " Ω" → set LabelCurrent.Text to join "Current I: " + local current + " A" → set LabelDrop1.Text to join "Voltage drop R1: " + (local current × (TextBoxR1.Text as number)) + " V" → set LabelDrop2.Text to join "Voltage drop R2: " + (local current × (TextBoxR2.Text as number)) + " V".

3) Blocks setup — check: after step 2, set LabelCheck.Text to join "Check: " + (drop1 + drop2) + " V — should equal " + TextBoxV.Text + " V" — compute drop1 + drop2 from the same local values, not by reading the labels back. Example: V = 20, R1 = 10, R2 = 20 → total 30 Ω, I = 0.67 A, drop1 = 6.67 V, drop2 = 13.33 V, check = 20 V.

4) Blocks setup — clear: when ButtonClear.Click → set TextBoxV.Text to "" → set TextBoxR1.Text to "" → set TextBoxR2.Text to "" → reset all four result labels to "—" → set LabelCheck.Text to "Check: drops add up to V".

5) Test: V = 20, R1 = 10, R2 = 20 → check the four numbers above (allow rounding to 2 decimal places); then V = 12, R1 = 10, R2 = 10 → total 20 Ω, I = 0.6 A, drops 6 V + 6 V = 12 V.

90-minute timing: 0–10 plan/sketch — draw a series circuit (battery, R1, R2 in a line) and label what the app must show; 10–20 demo — Rica works one example on paper; 20–65 build — total + current first, voltage drops second, check third; 65–80 test & fix — test both examples, fix rounding; 80–90 share — Gin calculates one circuit for Rica and explains why the drops add up to V. Test checklist: Example 1 gives 30 Ω, 0.67 A, 6.67 V, 13.33 V; example 2 gives 20 Ω, 0.6 A, 6 V, 6 V. Drops add to V in both. Common bug: current shows 0 or a huge number — fix: check the division is V ÷ total (not total ÷ V), and that all TextBox values were converted to numbers. Success check: Gin's calculator gives total R, current and both voltage drops, with the drops adding to V. Homework: Calculate on paper: V = 9 V, R1 = 10 Ω, R2 = 20 Ω, R3 = 30 Ω — what is the total? (Answer: 60 Ω, I = 0.15 A.) Bring it to add a third resistor next time.

Session 92Parallel circuit calculator — total resistance, branch currentsWed 16 Aug 2028
Wed 16 Aug 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 16 Aug 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a parallel circuit calculator that gives total resistance and each branch current from V, R1 and R2. Components: LabelTitle, Text "Parallel Circuit Calculator"; TextBoxV, Hint "Supply voltage V, e.g. 20"; TextBoxR1, Hint "Resistor 1 (Ω), e.g. 10"; TextBoxR2, Hint "Resistor 2 (Ω), e.g. 10"; ButtonCalc, Text "Calculate Parallel Circuit", FontSize 18; LabelTotal, Text "Total R: —", FontSize 16; LabelTotalCurrent, Text "Total current: —", FontSize 16; LabelBranch1, Text "Branch 1 current: —", FontSize 16; LabelBranch2, Text "Branch 2 current: —", FontSize 16; LabelCheck, Text "Check: branch currents add up to total current"; ButtonClear, Text "Clear", FontSize 16. Step-by-step build:

1) Designer setup: add the three TextBoxes, Calculate/Clear buttons and four result labels above; set Screen1 Title to "Parallel Calculator".

2) Blocks setup — calculate: when ButtonCalc.Click → if any TextBox is empty then set LabelTotal.Text to "Type V, R1 and R2 first" else set local r1 to TextBoxR1.Text as number → set local r2 to TextBoxR2.Text as number → set local totalR to 1 ÷ ((1 ÷ local r1) + (1 ÷ local r2)) → set LabelTotal.Text to join "Total R: " + local totalR + " Ω" → set local totalI to (TextBoxV.Text as number) ÷ local totalR → set LabelTotalCurrent.Text to join "Total current: " + local totalI + " A" → set LabelBranch1.Text to join "Branch 1 current: " + ((TextBoxV.Text as number) ÷ local r1) + " A" → set LabelBranch2.Text to join "Branch 2 current: " + ((TextBoxV.Text as number) ÷ local r2) + " A".

3) Blocks setup — check: set LabelCheck.Text to join "Check: " + (branch1 + branch2) + " A — should equal total " + local totalI + " A" — use the local numbers, not the label texts. Example: V = 20, R1 = 10, R2 = 10 → total 5 Ω, total current 4 A, branches 2 A + 2 A = 4 A. Second example: V = 20, R1 = 10, R2 = 20 → total 6.67 Ω, total 3 A, branches 2 A + 1 A = 3 A.

4) Blocks setup — clear: same as Session 91, resetting all TextBoxes and labels.

5) Test: both examples above, checking total R, total current and both branch currents, plus the check line.

90-minute timing: 0–10 plan/sketch — draw a parallel circuit (two branches side by side) and label total vs branch currents; 10–20 demo — Rica works one example on paper; 20–65 build — total R first, branch currents second, check third; 65–80 test & fix — test both examples; 80–90 share — Gin calculates one parallel circuit and explains why total R (5 Ω) is smaller than each branch (10 Ω). Test checklist: Example 1: 5 Ω, 4 A, 2 A + 2 A. Example 2: 6.67 Ω, 3 A, 2 A + 1 A. Branch currents add to total current. Common bug: total R comes out larger than R1 (e.g. 20 Ω) — fix: the parallel formula is 1 ÷ ((1 ÷ R1) + (1 ÷ R2)); if the result is bigger than the smallest resistor, the brackets are wrong — re-check step 2. Success check: Gin's calculator gives total R, total current and both branch currents, with branches adding to the total. Homework: Calculate on paper: V = 12 V, R1 = 10 Ω, R2 = 10 Ω — total R and branch currents? (Answers: 5 Ω, 1.2 A each, 2.4 A total.)

Session 93Circuit simulator logic — choose series / parallel, show diagram valuesWed 23 Aug 2028
Wed 23 Aug 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 23 Aug 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a circuit simulator screen: choose series or parallel, type V/R1/R2, and see the circuit type, totals and per-resistor values together. (Logic + labels, not a real physics engine.) Components: LabelTitle, Text "Circuit Simulator"; ButtonSeries, Text "Series", FontSize 18; ButtonParallel, Text "Parallel", FontSize 18; LabelMode, Text "Mode: — pick one", FontSize 16; Canvas1, Width 300, Height 150 (draw the circuit — see step 2); TextBoxV, Hint "Voltage V, e.g. 20"; TextBoxR1, Hint "R1 (Ω), e.g. 10"; TextBoxR2, Hint "R2 (Ω), e.g. 20"; ButtonSimulate, Text "Simulate", FontSize 18; LabelTotal, Text "Total R: —"; LabelCurrent, Text "Current: —"; LabelR1Value, Text "R1: —"; LabelR2Value, Text "R2: —"; LabelDiagram, Text "Diagram: —". Step-by-step build:

1) Designer setup: add the mode buttons, Canvas, TextBoxes, Simulate button and result labels above; set Screen1 Title to "Circuit Simulator"; add a global variable mode (text, "").

2) Blocks setup — choose mode + draw: when ButtonSeries.Click → set global mode to "Series" → set LabelMode.Text to "Mode: Series" → call Canvas1.Clear → [draw with Canvas blocks: a rectangle loop, two resistor zig-zags in a line, labels "R1" and "R2", a battery symbol] → set LabelDiagram.Text to "Diagram: battery — R1 — R2 in one line"; when ButtonParallel.Click → set global mode to "Parallel" → [same, but draw two branches side by side with R1 on the top branch and R2 on the bottom] → set LabelDiagram.Text to "Diagram: battery with R1 and R2 on separate branches".

3) Blocks setup — simulate: when ButtonSimulate.Click → if global mode = "" then set LabelTotal.Text to "Pick Series or Parallel first" else if any TextBox is empty then set LabelTotal.Text to "Type V, R1 and R2 first" else if global mode = "Series" then [Session 91 maths: total = R1 + R2; current = V ÷ total; R1 value = "drop " + (current × R1) + " V"; R2 value = "drop " + (current × R2) + " V"] else [Session 92 maths: total = 1 ÷ ((1 ÷ R1) + (1 ÷ R2)); total current = V ÷ total; R1 value = "branch " + (V ÷ R1) + " A"; R2 value = "branch " + (V ÷ R2) + " A"] → set LabelTotal.Text, LabelCurrent.Text, LabelR1Value.Text, LabelR2Value.Text from those locals.

4) Test: Series, V = 20, R1 = 10, R2 = 20 → 30 Ω, 0.67 A, drops 6.67 V / 13.33 V; switch to Parallel with the same values → 6.67 Ω, 3 A total, branches 2 A / 1 A; check the Canvas drawing changes with the mode.

90-minute timing: 0–10 plan/sketch — draw both circuits on paper; 10–20 demo — Rica switches modes and the diagram changes; 20–65 build — mode + drawing first, simulate maths second; 65–80 test & fix — test both modes with the same values, compare; 80–90 share — Gin simulates one series and one parallel circuit and explains which total is bigger and why. Test checklist: Picking a mode changes the diagram and LabelMode. Simulate with no mode → warning, not a crash. Series and parallel give the Session 91/92 numbers for the same inputs. Common bug: Simulate uses the series formula even in Parallel mode — fix: check the if global mode = "Series" … else block wraps the whole calculation, and that ButtonParallel actually sets global mode to "Parallel" (exact spelling). Success check: Gin's simulator shows the right diagram and values for both series and parallel. Homework: Add a third resistor input (R3) to the series side only, using the Session 91 homework answer (V = 9, 10 + 20 + 30 = 60 Ω). Needs / fallback: Needs no device, account, model or internet — Canvas drawing + maths blocks only. The Canvas drawing is a labelled sketch, not a measured schematic — Gin must be able to say the numbers come from his formulas, not from a simulation engine.

Session 94Power calculator — P = V × I, energy use, cost estimateWed 30 Aug 2028
Wed 30 Aug 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 30 Aug 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a power calculator: P = V × I, energy used over hours, and an estimated electricity cost. Components: LabelTitle, Text "Power Calculator"; TextBoxV, Hint "Voltage V, e.g. 20"; TextBoxI, Hint "Current I (A), e.g. 2"; ButtonCalcP, Text "Calculate Power", FontSize 18; LabelPower, Text "Power P: —", FontSize 18; TextBoxHours, Hint "Hours used, e.g. 5"; TextBoxRate, Hint "Price per kWh (THB), e.g. 5"; ButtonCalcCost, Text "Calculate Energy & Cost", FontSize 18; LabelEnergy, Text "Energy: —", FontSize 16; LabelCost, Text "Cost: —", FontSize 16; global variable powerW (number, 0). Step-by-step build:

1) Designer setup: add the TextBoxes, two Calculate buttons and three result labels above; set Screen1 Title to "Power Calculator".

2) Blocks setup — power: when ButtonCalcP.Click → if TextBoxV.Text = "" or TextBoxI.Text = "" then set LabelPower.Text to "Type V and I first" else set global powerW to (TextBoxV.Text as number) × (TextBoxI.Text as number) → set LabelPower.Text to join "Power P: " + global powerW + " W" — check: 20 × 2 = 40 W.

3) Blocks setup — energy + cost: when ButtonCalcCost.Click → if global powerW = 0 then set LabelEnergy.Text to "Calculate power first" else if TextBoxHours.Text = "" or TextBoxRate.Text = "" then set LabelEnergy.Text to "Type hours and price per kWh first" else set local energyKWh to (global powerW ÷ 1000) × (TextBoxHours.Text as number) → set LabelEnergy.Text to join "Energy: " + local energyKWh + " kWh" → set LabelCost.Text to join "Cost: " + (local energyKWh × (TextBoxRate.Text as number)) + " THB (estimate)" — check: 40 W × 5 h = 0.2 kWh; at 5 THB/kWh = 1 THB.

4) Blocks setup — also allow P from V and R: add ButtonCalcPFromR, Text "P from V and R"; when ButtonCalcPFromR.Click → [needs TextBoxR, Hint "Resistance R (Ω)"] → set global powerW to ((TextBoxV.Text as number) × (TextBoxV.Text as number)) ÷ (TextBoxR.Text as number) → set LabelPower.Text to join "Power P: " + global powerW + " W (from V² ÷ R)" — check: V = 20, R = 10 → 40 W, matching step 2.

5) Test: V = 20, I = 2 → 40 W; 5 hours at 5 THB/kWh → 0.2 kWh, 1 THB; then V = 10, I = 2 → 20 W, 10 hours at 5 THB/kWh → 0.2 kWh, 1 THB (same energy, different power — good discussion).

90-minute timing: 0–10 plan/sketch — list what the app needs (V, I, hours, price) and what it gives (W, kWh, THB); 10–20 demo — Rica works the 40 W example on paper; 20–65 build — power first, energy/cost second, V²÷R third; 65–80 test & fix — test both examples; 80–90 share — Gin prices running a 40 W device for 5 hours and explains why the answer is an estimate. Test checklist: 20 V × 2 A = 40 W; 40 W × 5 h = 0.2 kWh; 0.2 × 5 = 1 THB. Cost tapped before power → "Calculate power first". Common bug: energy shows 200 instead of 0.2 — fix: divide watts by 1000 to get kW before multiplying by hours; and check the rate is per kWh, not per hour. Success check: Gin's calculator gives power, energy and an estimated cost, with the estimate labelled as an estimate. Homework: Find one real device at home (check its label with an adult), note its watts, and calculate its cost for 3 hours at 5 THB/kWh. Needs / fallback: Needs no device, account, model or internet — maths blocks only. The electricity price is typed in by Gin (example 5 THB/kWh) — it is not fetched live, and the cost is always labelled "estimate" because real tariffs vary.

Session 95Timer & stopwatch app — start / stop / reset, lap timesWed 6 Sep 2028
Wed 6 Sep 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 6 Sep 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a timer and stopwatch app with start/stop/reset and saved lap times. Components: LabelTitle, Text "Timer & Stopwatch"; LabelTime, Text "00:00", FontSize 36; ButtonStart, Text "Start", FontSize 18; ButtonStop, Text "Stop", FontSize 18; ButtonReset, Text "Reset", FontSize 18; ButtonLap, Text "Lap", FontSize 18; ListViewLaps, ElementsFromString ""; LabelMode, Text "Mode: Stopwatch (count up)"; ButtonModeTimer, Text "Switch to Countdown Timer", FontSize 16; TextBoxSeconds, Hint "Countdown seconds, e.g. 60"; Clock1 (non-visible, TimerInterval 1000, TimerEnabled false); TinyDB1 (tag "laps"); global variables seconds (number, 0), isCountdown (boolean, false). Step-by-step build:

1) Designer setup: add the big time Label, four buttons, laps ListView, mode label/button and countdown TextBox; set Screen1 Title to "Timer & Stopwatch".

2) Blocks setup — display: procedure showTime → set local mins to floor(global seconds ÷ 60) → set local secs to global seconds − (local mins × 60) → set LabelTime.Text to join [if local mins < 10 then join "0" + local mins else local mins] + ":" + [if local secs < 10 then join "0" + local secs else local secs] — so 65 seconds shows 01:05.

3) Blocks setup — clock tick: when Clock1.Timer → if global isCountdown then set global seconds to global seconds − 1 → if global seconds <= 0 then set global seconds to 0 → call Clock1.TimerEnabled false → set LabelTime.Text to "Time's up!" else set global seconds to global seconds + 1 → call procedure showTime.

4) Blocks setup — buttons: when ButtonStart.Click → set Clock1.TimerEnabled to true; when ButtonStop.Click → set Clock1.TimerEnabled to false; when ButtonReset.Click → set Clock1.TimerEnabled to false → set global seconds to 0 → call procedure showTime; when ButtonLap.Click → add items to list [ListViewLaps.Elements] item join "Lap: " + LabelTime.Text → call TinyDB1.StoreValue tag "laps" valueToStore ListViewLaps.Elements.

5) Blocks setup — countdown mode: when ButtonModeTimer.Click → if global isCountdown then set global isCountdown to false → set LabelMode.Text to "Mode: Stopwatch (count up)" → set ButtonModeTimer.Text to "Switch to Countdown Timer" else set global isCountdown to true → if TextBoxSeconds.Text = "" then set global seconds to 60 else set global seconds to TextBoxSeconds.Text as number → set LabelMode.Text to "Mode: Countdown timer" → set ButtonModeTimer.Text to "Switch to Stopwatch" → call procedure showTime; when Screen1.Initialize → set ListViewLaps.Elements to call TinyDB1.GetValue tag "laps" valueIfTagNotThere create empty list.

6) Test: stopwatch — Start, wait 10 seconds, Lap, Stop, check LabelTime ≈ 00:10 and the lap saved; Reset → 00:00; countdown — type 10, switch mode, Start, wait → "Time's up!" at 0.

90-minute timing: 0–10 plan/sketch — draw the stopwatch screen and the countdown screen; 10–20 demo — Rica starts a 10-second countdown; 20–65 build — display + tick first, buttons second, countdown third; 65–80 test & fix — test stopwatch laps, then a 10-second countdown; 80–90 share — Gin times Rica doing a 30-second task with his stopwatch and reads the lap back. Test checklist: Stopwatch counts up in seconds and shows mm:ss. Lap saves and survives reopening. Countdown reaches 0 and stops with "Time's up!" (not negative numbers). Common bug: timer runs twice as fast — fix: check Clock1.TimerInterval is 1000 (1 second) and that Start was not tapped twice without Stop — set TimerEnabled false before setting it true in the Start handler, or disable Start while running. Success check: Gin's app works as a stopwatch with laps and as a countdown timer. Homework: Time how long it takes him to solve 5 Ohm's Law questions with the stopwatch, and save the laps.

Session 96Alarm / reminder app — set a time, notification (exploration)Wed 13 Sep 2028
Wed 13 Sep 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 13 Sep 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a reminder app: set a time and a message, and the app alerts him when the time arrives (in-app alert while the app is open). (Exploration.) Components: LabelTitle, Text "Reminder App"; TextBoxHour, Hint "Hour (0–23), e.g. 15"; TextBoxMinute, Hint "Minute (0–59), e.g. 30"; TextBoxMessage, Hint "Reminder, e.g. CIY class at 15:30"; ButtonSet, Text "Set Reminder", FontSize 18; LabelSet, Text "No reminder set", FontSize 16; LabelNow, Text "Now: —", FontSize 16; ButtonCancel, Text "Cancel Reminder", FontSize 16; ListViewReminders, ElementsFromString ""; Clock1 (non-visible, TimerInterval 1000, TimerEnabled true); TinyDB1 (tag "reminders"); Notifier1 (non-visible, for the alert); global variables alarmHour, alarmMinute (numbers, −1), alarmMessage (text, ""), alreadyRang (boolean, false). Step-by-step build:

1) Designer setup: add the hour/minute/message TextBoxes, Set/Cancel buttons, the two labels and the reminders ListView; set Screen1 Title to "Reminder App".

2) Blocks setup — set: when ButtonSet.Click → if TextBoxHour.Text = "" or TextBoxMinute.Text = "" or TextBoxMessage.Text = "" then set LabelSet.Text to "Fill in hour, minute and message first" else if (TextBoxHour.Text as number) < 0 or > 23 or (TextBoxMinute.Text as number) < 0 or > 59 then set LabelSet.Text to "Hour must be 0–23, minute 0–59" else set global alarmHour to TextBoxHour.Text as number → set global alarmMinute to TextBoxMinute.Text as number → set global alarmMessage to TextBoxMessage.Text → set global alreadyRang to false → set LabelSet.Text to join "Reminder set for " + global alarmHour + ":" + global alarmMinute + " — " + global alarmMessage → add items to list ListViewReminders.Elements item LabelSet.Text → call TinyDB1.StoreValue tag "reminders" valueToStore ListViewReminders.Elements.

3) Blocks setup — check every second: when Clock1.Timer → set LabelNow.Text to join "Now: " + call Clock1.Now → set local nowHour to call Clock1.Hour → set local nowMinute to call Clock1.Minute → if not global alreadyRang and global alarmHour = local nowHour and global alarmMinute = local nowMinute then set global alreadyRang to true → call Notifier1.ShowAlert notice global alarmMessage → set LabelSet.Text to join "🔔 Reminder: " + global alarmMessage.

4) Blocks setup — cancel + load: when ButtonCancel.Click → set global alarmHour to −1 → set global alarmMinute to −1 → set global alreadyRang to false → set LabelSet.Text to "No reminder set"; when Screen1.Initialize → set ListViewReminders.Elements to call TinyDB1.GetValue tag "reminders" valueIfTagNotThere create empty list.

5) Test: set a reminder for 2 minutes from now (check the phone clock first), keep the app open, wait — the Notifier alert must pop up at that minute; tap Cancel on a second reminder and check it does not ring.

90-minute timing: 0–10 plan/sketch — list 3 reminders Gin would actually use (class, homework, charging); 10–20 demo — Rica sets a 2-minute reminder live; 20–65 build — set + validation first, clock check second, cancel third; 65–80 test & fix — test the 2-minute reminder, then a cancelled one; 80–90 share — Gin sets a reminder for his next class time and explains the limit below. Test checklist: Reminder set for 2 minutes ahead rings on time with the right message. Invalid hour (e.g. 25) → warning, no reminder set. Cancelled reminder does not ring. Common bug: the alert fires every second for a whole minute — fix: the alreadyRang flag in step 3 (set true the first time it rings, reset false only when a new reminder is set). Success check: Gin's app rings an in-app alert at the set time with the right message. Homework: Set a real reminder for tomorrow's class/homework time and note whether it rang. Needs / fallback: Exploration — this is an in-app reminder only: the Clock checks the time while the app is open. It is NOT a real phone alarm: if the app is closed or the phone is asleep, it will not ring — Gin must be told this plainly, and must not rely on it for anything important. No account, permission or background service is invented here. Fallback: if the Notifier alert does not show, use a big Label + TextToSpeech ("Reminder: …") as the alert instead — same trigger, different signal.

Session 97Calendar / planner app — add events, view by dayWed 20 Sep 2028
Wed 20 Sep 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 20 Sep 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build an app that stores events by date and shows only the events for the day he picks. Components: LabelTitle, Text "My Planner", FontSize 22, Bold true; DatePicker1 (non-visible picker, or use a TextBox for the date); TextBoxEvent, Hint "Event, e.g. CIY 15:30"; ButtonAdd, Text "Add event"; ButtonShow, Text "Show this day"; ListViewEvents; TinyDB1; LabelDay, Text "Pick a day"; LabelCount, Text "". Step-by-step build:

1) Designer setup: Title label at top; a TextBoxDate (Hint "Day, e.g. 20 Sep 2028") or a DatePicker; TextBoxEvent below it; Add and Show buttons side by side in a HorizontalArrangement; ListViewEvents below; LabelCount at the bottom. Add TinyDB1 (non-visible).

2) Blocks setup: a) global variable eventList = create empty list; global variable currentDate = "". b) when Screen1.Initialize → set currentDate to call Clock1.Now (or leave blank for manual entry) → call loadDay. c) when ButtonAdd.Click → if TextBoxEvent.Text ≠ "" then → add item (join TextBoxDate.Text + ": " + TextBoxEvent.Text) to list eventList → call TinyDB1.StoreValue tag (join "events_" + TextBoxDate.Text) valueToStore eventList → set TextBoxEvent.Text to "" → call loadDay. d) when ButtonShow.Click → set currentDate to TextBoxDate.Text → call loadDay. e) procedure loadDay → set eventList to call TinyDB1.GetValue tag (join "events_" + currentDate) valueIfTagNotThere (create empty list) → set ListViewEvents.Elements to eventList → set LabelCount.Text to (join length of list eventList + " event(s) on " + currentDate).

3) Test: add "CIY 15:30" and "Homework: resistor quiz" for 20 Sep 2028, switch the date to 21 Sep 2028, check the list is empty, switch back and check both events return.

90-minute timing: 0–10 plan/sketch — sketch the day view and decide the date format; 10–20 demo — Rica shows a paper planner and one saved event loading; 20–65 build; 65–80 test & fix; 80–90 share — show Ray and Run the planner with a real CIY day in it. Test checklist: Add an event, close and reopen the app, tap Show — is the event still there? Add an event with an empty text box — nothing should be added. Check the count label matches the list length. Common bug: events from every day show at once — fix: the TinyDB tag must include the date ("events_" + date), so each day has its own tag. Success check: Gin can add two events for one day, view that day only, and reload them after closing the app. Homework: Add his real CIY Wednesdays for the next two weeks into the planner.

Session 98Password / PIN app — simple PIN lock, TinyDB (exploration, no real security)Wed 27 Sep 2028
Wed 27 Sep 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 27 Sep 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a simple 4-digit PIN lock screen that checks a stored PIN with TinyDB — and can explain why it is NOT real security. Components: LabelTitle, Text "PIN Lock (practice only)", FontSize 20; PasswordTextBoxPIN, Hint "Enter 4-digit PIN", NumbersOnly true; ButtonUnlock, Text "Unlock"; ButtonSetPIN, Text "Set / change PIN"; LabelResult, Text "", FontSize 18; LabelWarning, Text "Practice lock only — NOT real security", TextColor Red; TinyDB1; LabelSecret, Text "🔓 Unlocked! My notes: CIY Wed 15:30", Visible false. Step-by-step build:

1) Designer setup: Warning label at the very top in red; PIN text box (PasswordTextBox hides the digits); Unlock and Set PIN buttons; result label; a hidden LabelSecret that only shows after a correct PIN. Add TinyDB1.

2) Blocks setup: a) global variable savedPIN = "". b) when Screen1.Initialize → set savedPIN to call TinyDB1.GetValue tag "pin" valueIfTagNotThere "1234" → if savedPIN = "1234" then set LabelResult.Text to "First time: default PIN is 1234 — change it!". c) when ButtonUnlock.Click → if PasswordTextBoxPIN.Text = savedPIN then → set LabelSecret.Visible to true → set LabelResult.Text to "Unlocked!" → set PasswordTextBoxPIN.Text to "" else → set LabelResult.Text to "Wrong PIN — try again" → set LabelSecret.Visible to false. d) when ButtonSetPIN.Click → if length of text PasswordTextBoxPIN.Text = 4 then → call TinyDB1.StoreValue tag "pin" valueToStore PasswordTextBoxPIN.Text → set savedPIN to PasswordTextBoxPIN.Text → set LabelResult.Text to "PIN saved (on this phone only)" else → set LabelResult.Text to "PIN must be exactly 4 digits".

3) Test: unlock with 1234, change the PIN to 2028, close and reopen, unlock with 2028, try a wrong PIN and check the secret stays hidden.

90-minute timing: 0–10 plan/sketch — sketch lock screen and unlocked screen; 10–20 demo — Rica shows the default PIN flow and the warning; 20–65 build; 65–80 test & fix; 80–90 share — demo the lock to Ray and Run and explain the warning in his own words. Test checklist: Wrong PIN hides the secret; correct PIN shows it; new PIN survives closing the app; a 3-digit PIN is rejected with the message. Common bug: the PIN works once but resets to 1234 after reopening — fix: Screen1.Initialize must read the PIN from TinyDB1, not set it to "1234" every time; only use "1234" as the valueIfTagNotThere. Success check: Gin can set a 4-digit PIN, lock and unlock the app, and explain that anyone with the phone or the .aia file can read the PIN, so it must never protect real secrets. Homework: Write down in one sentence why this lock is only for practice, and think of one place a real PIN is needed (phone lock screen, bank app).

Session 99Unit converter — length, mass, temperature, electronics unitsWed 4 Oct 2028
Wed 4 Oct 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 4 Oct 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a converter that turns one value into another unit using a Spinner choice and maths blocks. Components: LabelTitle, Text "Unit Converter", FontSize 22; SpinnerType, Elements "Length,Mass,Temperature,Electronics"; SpinnerFrom, Elements set by blocks; SpinnerTo, Elements set by blocks; TextBoxValue, Hint "Enter a number", NumbersOnly true; ButtonConvert, Text "Convert"; LabelResult, Text "", FontSize 20, Bold true; LabelFormula, Text "". Step-by-step build:

1) Designer setup: Title; SpinnerType at top; two Spinners (From / To) in a HorizontalArrangement with a "→" label between them; value TextBox; Convert button; big result label; small formula label under it.

2) Blocks setup: a) global lists: lengthUnits = make a list ("m", "cm", "mm", "km"); massUnits = make a list ("kg", "g", "mg"); tempUnits = make a list ("°C", "°F", "K"); elecUnits = make a list ("Ω", "kΩ", "MΩ", "mA", "A"). b) when SpinnerType.AfterSelecting → if selection = "Length" then set SpinnerFrom.Elements to lengthUnits, SpinnerTo.Elements to lengthUnits (repeat for each type with its list). c) when ButtonConvert.Click → set global input to TextBoxValue.Text as number → if SpinnerType.Selection = "Temperature" then handle separately: if From "°C" and To "°F" → result = (input × 9 ÷ 5) + 32; if From "°F" and To "°C" → result = (input − 32) × 5 ÷ 9; if From "°C" and To "K" → result = input + 273.15; if same unit → result = input — else use a factor table: if From "cm" and To "m" → result = input ÷ 100; if From "m" and To "cm" → result = input × 100; if From "kΩ" and To "Ω" → result = input × 1000; if From "Ω" and To "kΩ" → result = input ÷ 1000; if From "A" and To "mA" → result = input × 1000; if From = To → result = input. d) set LabelResult.Text to (join input + " " + From + " = " + result + " " + To) → set LabelFormula.Text to the rule used, e.g. "°C to °F: × 9 ÷ 5, then + 32".

3) Test: 100 cm → 1 m; 25 °C → 77 °F; 2.2 kΩ → 2200 Ω; 1 A → 1000 mA; same-unit conversion returns the same number.

90-minute timing: 0–10 plan/sketch — list the four unit groups and two conversions each; 10–20 demo — Rica converts 25 °C and 2.2 kΩ by hand first; 20–65 build; 65–80 test & fix; 80–90 share — challenge Ray and Run to stump the converter. Test checklist: Each SpinnerType choice changes both unit lists; temperature conversions match known values (0 °C = 32 °F, 100 °C = 212 °F); electronics conversions match resistor values Gin already knows (4.7 kΩ = 4700 Ω). Common bug: converting °C to °F gives a wrong number — fix: check the order of blocks, (input × 9 ÷ 5) + 32, not input × 9 ÷ (5 + 32); maths blocks follow the order they are nested in. Success check: Gin can convert correctly in all four groups and explain why temperature needs a formula, not just × or ÷. Homework: Add one more conversion pair of his choice (e.g. km ↔ m, g ↔ kg) to the blocks.

Session 100Maths helper — fractions, percentages, averagesWed 11 Oct 2028
Wed 11 Oct 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 11 Oct 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a maths helper that simplifies a fraction, works out a percentage, and finds the average of a list of numbers. Components: LabelTitle, Text "Maths Helper", FontSize 22; SpinnerMode, Elements "Fraction,Percentage,Average"; TextBoxA, Hint "First number"; TextBoxB, Hint "Second number (or list: 4, 6, 8)"; ButtonSolve, Text "Solve"; LabelResult, Text "", FontSize 20, Bold true; LabelSteps, Text "", FontSize 16. Step-by-step build:

1) Designer setup: Title; SpinnerMode; two TextBoxes (A and B — B doubles as a comma-separated list for Average); Solve button; big result label; steps label underneath showing the working.

2) Blocks setup: a) when ButtonSolve.Click → if SpinnerMode.Selection = "Fraction" then → set global num to TextBoxA.Text, global den to TextBoxB.Text → set global g to (greatest common divisor — loop: set g to num, while den ≠ 0 repeat with remainder blocks, or use the simple check: try divisors 2–10 in an if/else chain) → set LabelResult.Text to (join (num ÷ g) + "/" + (den ÷ g)) → set LabelSteps.Text to (join "Divided top and bottom by " + g). b) if Selection = "Percentage" then → set result to (TextBoxA.Text ÷ TextBoxB.Text × 100) → set LabelResult.Text to (join result + "%") → set LabelSteps.Text to (join TextBoxA.Text + " ÷ " + TextBoxB.Text + " × 100") — example: 45 out of 60 = 75%. c) if Selection = "Average" then → set global nums to split TextBoxB.Text at "," → set global total to 0 → for each item in nums → set total to total + item → set result to total ÷ length of list nums → set LabelResult.Text to (join "Average = " + result) → set LabelSteps.Text to (join "Total " + total + " ÷ " + length of list nums + " numbers").

3) Test: 12/16 → 3/4; 45 out of 60 → 75%; average of 4, 6, 8 → 6; average of his last three quiz scores.

90-minute timing: 0–10 plan/sketch — work one example of each mode on paper; 10–20 demo — Rica shows the fraction simplifying by hand; 20–65 build; 65–80 test & fix; 80–90 share — quiz Ray and Run with the helper. Test checklist: 12/16 simplifies to 3/4, not 12/16; 45/60 gives 75%; average of 4, 6, 8 gives 6; typing letters shows a friendly message, not a crash. Common bug: percentage shows 0.75 instead of 75 — fix: multiply by 100 before showing, and add the "%" in the join block, not in the maths. Success check: Gin can solve one problem in each mode and show the working steps under the answer. Homework: Use the Average mode on three real numbers from his week (e.g. three quiz scores or three resistor readings).

Session 101Science helper — periodic / formula lookup appWed 18 Oct 2028
Wed 18 Oct 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 18 Oct 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a lookup app that finds an element or a formula from a list and shows its facts. Components: LabelTitle, Text "Science Helper", FontSize 22; SpinnerTopic, Elements "Elements,Formulas"; ListPickerElement, Text "Pick an element"; LabelName, Text "", FontSize 20, Bold true; LabelFacts, Text "", FontSize 16; TextBoxSearch, Hint "Or type a symbol, e.g. Fe"; ButtonSearch, Text "Search". Step-by-step build:

1) Designer setup: Title; SpinnerTopic; ListPicker for elements; search TextBox + button; a big name label and a facts label below. Keep the layout simple so the facts are easy to read.

2) Blocks setup: a) global lists: elementNames = make a list ("Hydrogen", "Oxygen", "Iron", "Copper", "Silicon", "Carbon"); elementSymbols = make a list ("H", "O", "Fe", "Cu", "Si", "C"); elementFacts = make a list ("H — lightest gas, 1 proton", "O — gas we breathe, 8 protons", "Fe — iron, used in wires and magnets", "Cu — copper, best common wire metal", "Si — silicon, inside computer chips", "C — carbon, in pencils and diamonds"); formulaNames = make a list ("Ohm's Law", "Power", "Speed", "Area of a circle"); formulaTexts = make a list ("V = I × R", "P = V × I", "speed = distance ÷ time", "A = π × r²"). b) when ListPickerElement.BeforePicking → set ListPickerElement.Elements to elementNames. c) when ListPickerElement.AfterPicking → set global i to index in list elementNames of ListPickerElement.Selection → set LabelName.Text to ListPickerElement.Selection → set LabelFacts.Text to select list item elementFacts index i. d) when ButtonSearch.Click → set global j to index in list elementSymbols of TextBoxSearch.Text → if j > 0 then set LabelName.Text to select list item elementNames index j, LabelFacts.Text to select list item elementFacts index j else set LabelFacts.Text to "Not in this list yet — try H, O, Fe, Cu, Si or C". e) when SpinnerTopic.AfterSelecting → if selection = "Formulas" then set ListPickerElement.Elements to formulaNames and show formula text the same way with formulaTexts (same index pattern).

3) Test: pick Iron → shows Fe facts; type "Cu" → shows Copper; pick "Ohm's Law" in Formulas → shows V = I × R; type "Xx" → friendly "not in this list" message.

90-minute timing: 0–10 plan/sketch — pick the 6 elements and 4 formulas to include; 10–20 demo — Rica looks up copper by hand from the list; 20–65 build; 65–80 test & fix; 80–90 share — ask Ray and Run to pick an element and check the facts. Test checklist: Every element in the picker shows the matching facts (not the next one's); search is case-sensitive-safe (try "fe" — if it fails, add a note or an upcase block); Formulas mode swaps the picker list. Common bug: facts are off by one — fix: the three lists must stay in the same order, and the index comes from index in list of the name list, then is used on the facts list. Success check: Gin can look up any of the 6 elements two ways (picker and search) and any formula, with matching facts every time. Homework: Add two more elements (e.g. Gold Au, Aluminium Al) to all three lists, in the same order.

Session 102Language helper — Thai–English word flashcards with soundWed 25 Oct 2028
Wed 25 Oct 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 25 Oct 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build Thai–English flashcards that show a word, flip to its translation, and speak it aloud. Components: LabelTitle, Text "Thai–English Flashcards", FontSize 22; LabelCard, Text "สวัสดี", FontSize 32, Bold true; ButtonFlip, Text "Flip — show English"; ButtonNext, Text "Next word"; ButtonSpeak, Text "🔊 Hear it"; TextToSpeech1; LabelProgress, Text "1 of 10"; ButtonShuffle, Text "Shuffle". Step-by-step build:

1) Designer setup: Big card label in the middle (large font so Thai script is readable); Flip, Next and Hear it buttons in a row; progress label at the bottom; Shuffle button. Add TextToSpeech1 (non-visible).

2) Blocks setup: a) global lists: thaiWords = make a list ("สวัสดี", "ขอบคุณ", "วงจร", "ตัวต้านทาน", "แรงดันไฟฟ้า", "กระแสไฟฟ้า", "คอมพิวเตอร์", "สวัสดีตอนเช้า"); englishWords = make a list ("Hello", "Thank you", "Circuit", "Resistor", "Voltage", "Current", "Computer", "Good morning"); global variable cardIndex = 1; global variable showingThai = true. b) procedure showCard → set LabelCard.Text to select list item thaiWords index cardIndex → set showingThai to true → set LabelProgress.Text to (join "Card " + cardIndex + " of " + length of list thaiWords). c) when Screen1.Initialize → call showCard. d) when ButtonFlip.Click → if showingThai then set LabelCard.Text to select list item englishWords index cardIndex, set showingThai to false, set ButtonFlip.Text to "Flip — show Thai" else call showCard, set ButtonFlip.Text to "Flip — show English". e) when ButtonNext.Click → set cardIndex to cardIndex + 1 → if cardIndex > length of list thaiWords then set cardIndex to 1 → call showCard. f) when ButtonSpeak.Click → if showingThai then call TextToSpeech1.Speak message (select list item thaiWords index cardIndex) language "th" else call TextToSpeech1.Speak message (select list item englishWords index cardIndex) language "en". g) when ButtonShuffle.Click → set cardIndex to random integer from 1 to length of list thaiWords → call showCard.

3) Test: flip สวัสดี → Hello; hear it in Thai, flip, hear it in English; Next past the last card wraps to card 1; Shuffle jumps to a random card.

90-minute timing: 0–10 plan/sketch — choose 8 words, half everyday and half electronics; 10–20 demo — Rica flips one card and speaks it; 20–65 build; 65–80 test & fix; 80–90 share — test Ray and Run on the electronics words. Test checklist: Thai and English always match (same index); sound speaks the language shown on the card; Next wraps around instead of crashing on card 9; progress label is always correct. Common bug: after Shuffle, Flip shows the wrong English word — fix: Flip must use the same cardIndex as the card shown; never change cardIndex inside the Flip block. Success check: Gin can flip, hear, and move through all 8 cards with matching Thai–English pairs and correct sound. Homework: Add 4 more words of his choice (Thai + English) to both lists, in the same order.

Session 103Budget / money tracker — add spending, total, save with TinyDBWed 1 Nov 2028
Wed 1 Nov 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 1 Nov 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a money tracker that adds spending entries, totals them, and saves everything with TinyDB. Components: LabelTitle, Text "My Money Tracker", FontSize 22; TextBoxWhat, Hint "What did you buy?"; TextBoxAmount, Hint "Amount (THB)", NumbersOnly true; ButtonAdd, Text "Add spending"; ListViewSpending; LabelTotal, Text "Total spent: 0 THB", FontSize 20, Bold true; ButtonClear, Text "Clear all"; TinyDB1; LabelBudget, Text "Budget: 500 THB", FontSize 16. Step-by-step build:

1) Designer setup: Title; budget label; two TextBoxes (what + amount); Add button; ListView of spending; big total label; Clear button at the bottom. Add TinyDB1.

2) Blocks setup: a) global variable spendingList = create empty list; global variable total = 0; global variable budget = 500. b) when Screen1.Initialize → set spendingList to call TinyDB1.GetValue tag "spending" valueIfTagNotThere (create empty list) → call updateTotal. c) procedure updateTotal → set total to 0 → for each item in spendingList → set total to total + (second part of item) — store each entry as a joined text like "Snack — 45" and keep a parallel list amountList of numbers; simpler: keep two lists, spendingList (text) and amountList (numbers), saved under tags "spending" and "amounts". → set LabelTotal.Text to (join "Total spent: " + total + " THB — " + (budget − total) + " THB left") → if total > budget then set LabelTotal.TextColor to Red else set LabelTotal.TextColor to Black. d) when ButtonAdd.Click → if TextBoxWhat.Text ≠ "" and TextBoxAmount.Text ≠ "" then → add item (join TextBoxWhat.Text + " — " + TextBoxAmount.Text + " THB") to list spendingList → add item TextBoxAmount.Text as number to list amountList → call TinyDB1.StoreValue tag "spending" valueToStore spendingList → call TinyDB1.StoreValue tag "amounts" valueToStore amountList → set ListViewSpending.Elements to spendingList → call updateTotal → set TextBoxWhat.Text to "" → set TextBoxAmount.Text to "". e) when ButtonClear.Click → set spendingList to create empty list → set amountList to create empty list → call TinyDB1.ClearAll (or store empty lists under both tags) → set ListViewSpending.Elements to spendingList → call updateTotal.

3) Test: add Snack 45, Drink 25, Notebook 60 → total 130, 370 left; close and reopen → all three entries and the total are back; add an entry that pushes the total over 500 → total turns red.

90-minute timing: 0–10 plan/sketch — sketch the tracker and set a budget number; 10–20 demo — Rica adds two entries on paper and totals them; 20–65 build; 65–80 test & fix; 80–90 share — show Ray and Run the running total and the red over-budget warning. Test checklist: Total is the true sum, not the last amount; entries survive closing the app; Clear empties both the list and the total; over-budget turns the total red. Common bug: total shows 452560 instead of 130 — fix: the amounts are being joined as text, not added as numbers; use the + maths block on numbers from amountList, and store numbers, not text, in that list. Success check: Gin can add spending, see a correct running total and remaining budget, and reload it all after closing the app. Homework: Track his real spending for three days and bring the list to the next session.

Session 104Health tracker — log water / exercise, show a chart (blocks chart)Wed 8 Nov 2028
Wed 8 Nov 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 8 Nov 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a health tracker that logs glasses of water and minutes of exercise and shows the week as a blocks-drawn bar chart. Components: LabelTitle, Text "My Health Tracker", FontSize 22; ButtonWater, Text "+1 glass of water 💧"; ButtonExercise, Text "+10 min exercise 🏃"; LabelWater, Text "Water today: 0 glasses", FontSize 18; LabelExercise, Text "Exercise today: 0 min", FontSize 18; Canvas1, Width Fill parent, Height 200 pixels, BackgroundColor White; ButtonResetDay, Text "New day — reset"; TinyDB1; LabelGoal, Text "Goal: 8 glasses, 30 min". Step-by-step build:

1) Designer setup: Title; goal label; two big log buttons; two count labels; a Canvas for the chart; reset button. Add TinyDB1. The chart is drawn with blocks on the Canvas, not a chart component.

2) Blocks setup: a) global variables waterToday = 0, exerciseToday = 0; global list weekWater = make a list (0, 0, 0, 0, 0, 0, 0) (7 days). b) when Screen1.Initialize → set waterToday to call TinyDB1.GetValue tag "water" valueIfTagNotThere 0 → set exerciseToday to call TinyDB1.GetValue tag "exercise" valueIfTagNotThere 0 → set weekWater to call TinyDB1.GetValue tag "weekWater" valueIfTagNotThere (make a list (0,0,0,0,0,0,0)) → call updateLabels → call drawChart. c) when ButtonWater.Click → set waterToday to waterToday + 1 → call TinyDB1.StoreValue tag "water" valueToStore waterToday → call updateLabels → call drawChart. d) when ButtonExercise.Click → set exerciseToday to exerciseToday + 10 → store the same way → call updateLabels. e) procedure updateLabels → set LabelWater.Text to (join "Water today: " + waterToday + " glasses") → set LabelExercise.Text to (join "Exercise today: " + exerciseToday + " min") → if waterToday ≥ 8 then set LabelWater.TextColor to Green. f) procedure drawChart → call Canvas1.Clear → for each number i from 1 to 7 → set barHeight to (select list item weekWater index i) × 15 → call Canvas1.DrawShape (or DrawLine/rectangle via FillRect) at x = i × 40, y = 180 − barHeight, width 30, height barHeight, fillColor Blue — set replace list item weekWater index 7 to waterToday before drawing so today is the last bar. g) when ButtonResetDay.Click → set waterToday to 0 → set exerciseToday to 0 → store both → call updateLabels → call drawChart.

3) Test: tap water 3 times → "3 glasses"; tap exercise twice → "20 min"; the last chart bar grows; close and reopen → counts are back; reach 8 glasses → label turns green.

90-minute timing: 0–10 plan/sketch — sketch the two counters and the 7-bar chart; 10–20 demo — Rica draws a 3-bar chart on paper first; 20–65 build; 65–80 test & fix; 80–90 share — show Ray and Run the chart and explain what each bar means. Test checklist: Counts survive closing the app; the chart's last bar matches today's water count; reset zeroes today but the chart still shows the week; 8 glasses turns the label green. Common bug: the chart draws nothing — fix: drawChart must run after Screen1.Initialize loads the list, and Canvas coordinates start at the top-left, so the bar's y must be 180 − barHeight, not barHeight. Success check: Gin can log water and exercise, see the counts and a 7-bar chart that matches them, and reload them after closing the app. Homework: Log his real water and exercise for three days and check the chart each evening.

Session 105Chart app — bar chart from a list of numbersWed 15 Nov 2028
Wed 15 Nov 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 15 Nov 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a chart app that takes a list of numbers and draws a labelled bar chart on a Canvas. Components: LabelTitle, Text "Bar Chart Maker", FontSize 22; TextBoxNumbers, Hint "Numbers, e.g. 4, 7, 2, 9"; TextBoxLabels, Hint "Labels, e.g. Mon, Tue, Wed, Thu"; ButtonDraw, Text "Draw chart"; Canvas1, Width Fill parent, Height 250 pixels, BackgroundColor White; ButtonSample, Text "Try sample data"; LabelMax, Text "". Step-by-step build:

1) Designer setup: Title; two TextBoxes (numbers, then labels); Draw and Sample buttons side by side; a tall Canvas; a small label under the canvas for the biggest value.

2) Blocks setup: a) global variables numList = create empty list, labelList = create empty list. b) when ButtonSample.Click → set TextBoxNumbers.Text to "4, 7, 2, 9, 5" → set TextBoxLabels.Text to "Mon, Tue, Wed, Thu, Fri" → call drawChartFromBoxes. c) when ButtonDraw.Click → call drawChartFromBoxes. d) procedure drawChartFromBoxes → set numList to split TextBoxNumbers.Text at "," → set labelList to split TextBoxLabels.Text at "," → call Canvas1.Clear → set global maxVal to 0 → for each item in numList → if item > maxVal then set maxVal to item → set LabelMax.Text to (join "Biggest value: " + maxVal) → for each number i from 1 to length of list numList → set barHeight to (select list item numList index i) ÷ maxVal × 200 → call Canvas1.DrawShape/FillRect at x = 20 + (i − 1) × 60, y = 230 − barHeight, width 40, height barHeight, fillColor (pick a colour by i: Blue, Green, Orange, Red, Purple) → call Canvas1.DrawText text (select list item labelList index i) at x = 20 + (i − 1) × 60, y = 240 → call Canvas1.DrawText text (select list item numList index i) at x = 20 + (i − 1) × 60, y = 220 − barHeight.

3) Test: sample data draws 5 bars with Mon–Fri labels and 9 as the tallest; enter 10, 10, 10 → three equal bars; enter a single number → one bar; enter more labels than numbers → no crash.

90-minute timing: 0–10 plan/sketch — sketch a 5-bar chart with labels and values; 10–20 demo — Rica draws the sample chart on paper with heights to scale; 20–65 build; 65–80 test & fix; 80–90 share — chart Ray and Run's scores from a quick game and show the result. Test checklist: Bar heights are in proportion (9 is taller than 2, roughly 4×); every bar has its label under it and its value above it; equal numbers give equal bars; the tallest bar never runs off the top of the Canvas. Common bug: bars run off the top or look tiny — fix: scale every height with value ÷ maxVal × 200, so the biggest value always fills the canvas height; never use the raw number as the height. Success check: Gin can type any list of numbers and labels and get a correct, labelled, scaled bar chart. Homework: Chart one real list from his week (e.g. daily water glasses from Session 104, or quiz scores).

Session 106Map app — show a place, markers (exploration)Wed 22 Nov 2028
Wed 22 Nov 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 22 Nov 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can build a map app that shows places with markers — and can explain that maps need a device and internet, with an offline list fallback. Components: LabelTitle, Text "My Places Map", FontSize 22; Map1 (Google Maps component), Width Fill parent, Height 300 pixels, Latitude 13.7563, Longitude 100.5018, ZoomLevel 12; ButtonHome, Text "📍 CIY Club"; ButtonSchool, Text "📍 School"; ButtonPark, Text "📍 Park"; LabelPlace, Text "Tap a button to jump to a place", FontSize 16; ListViewPlaces (offline fallback list); LabelNote, Text "Maps need internet + location on. No internet? Use the list below.", FontSize 14. Step-by-step build:

1) Designer setup: Title; the Map component; three place buttons in a row; a place label; the note label; a ListView of places underneath as the offline fallback. Set the map's starting centre to Bangkok (13.7563, 100.5018) — adjust the real place coordinates with Rica on the day.

2) Blocks setup: a) global lists: placeNames = make a list ("CIY Club", "School", "Park", "Home"); placeLats = make a list (13.7563, 13.7563, 13.7563, 13.7563) — replace with real coordinates found on the day; placeLons = make a list (100.5018, 100.5018, 100.5018, 100.5018). b) when Screen1.Initialize → set ListViewPlaces.Elements to placeNames → call Map1.AddMarker latitude 13.7563 longitude 100.5018 title "Bangkok — start here". c) procedure goToPlace index i → call Map1.PanTo latitude (select list item placeLats index i) longitude (select list item placeLons index i) → call Map1.AddMarker latitude (select list item placeLats index i) longitude (select list item placeLons index i) title (select list item placeNames index i) → set LabelPlace.Text to (join "Showing: " + select list item placeNames index i). d) when ButtonHome.Click → call goToPlace 1 (and the same for School = 2, Park = 3). e) when ListViewPlaces.AfterPicking → call goToPlace (index in list placeNames of ListViewPlaces.Selection) — this is the offline fallback path: the list works and shows the place name even when the map tiles cannot load. f) If the map fails to load, the app still shows the place list and the note label — nothing crashes.

3) Test: tap each button — the map moves and a marker appears; tap a list item — same place shows; turn off Wi-Fi/data if Rica allows — the list still works and the note explains why the map is blank.

90-minute timing: 0–10 plan/sketch — list 4 real places and find their coordinates together; 10–20 demo — Rica shows a map moving to a marker; 20–65 build; 65–80 test & fix; 80–90 share — show Ray and Run the four places on the map. Test checklist: Each button moves the map to a different place with a marker; the list and the buttons agree; with no internet the list still opens and the note is visible. Common bug: the map stays blank or grey — fix: this is usually no internet or no location permission, not a blocks bug; check Wi-Fi, check the app's location permission, and use the list fallback — do not keep rebuilding the blocks. Success check: Gin can jump to four places with markers, explain plainly that maps need a device and internet, and show the offline list of places when the map cannot load. Homework: Find the real latitude/longitude of two places he goes to (with Rica's help) and add them to the lists.

Session 107Advanced UI — tabs, side menu, polished layoutWed 29 Nov 2028
Wed 29 Nov 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 29 Nov 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can rebuild one of his own apps with a polished layout: tabs across the top, a side menu, and consistent colours and spacing. Components: LabelTitle, Text "My App — new look", FontSize 22; HorizontalArrangementTabs with ButtonTabHome, ButtonTabTools, ButtonTabAbout, each Text "Home/Tools/About", BackgroundColor LightGray; VerticalArrangementHome, Visible true; VerticalArrangementTools, Visible false; VerticalArrangementAbout, Visible false; ButtonMenu, Text "☰ Menu"; VerticalArrangementSideMenu, Visible false, with ButtonMenuCalc, Text "Calculator", ButtonMenuQuiz, Text "Quiz", ButtonMenuClose, Text "✕ Close menu"; LabelContent, Text "Welcome! Pick a tab or open the menu.". Step-by-step build:

1) Designer setup: Pick the app to restyle — his Ohm's Law calculator or quiz app is ideal. Title at top; a row of three tab buttons; three VerticalArrangements stacked in the same space, only Home visible; a ☰ menu button; a side-menu VerticalArrangement (narrow, left side) hidden by default with two shortcut buttons and a close button. Set one accent colour (e.g. Blue) and one background colour, and use them on every button.

2) Blocks setup: a) procedure showTab tabName → set VerticalArrangementHome.Visible to (tabName = "Home") → set VerticalArrangementTools.Visible to (tabName = "Tools") → set VerticalArrangementAbout.Visible to (tabName = "About") → set ButtonTabHome.BackgroundColor to (if tabName = "Home" then Blue else LightGray) — repeat the colour line for the other two tab buttons. b) when ButtonTabHome.Click → call showTab "Home" (same for Tools and About). c) when ButtonMenu.Click → set VerticalArrangementSideMenu.Visible to true. d) when ButtonMenuClose.Click → set VerticalArrangementSideMenu.Visible to false. e) when ButtonMenuCalc.Click → set VerticalArrangementSideMenu.Visible to false → call showTab "Tools" (and ButtonMenuQuiz → showTab "Home" or open the quiz screen). f) Move the original app's working blocks into the right arrangement — the calculator blocks stay exactly as they were, only their screen position changes.

3) Test: tap each tab — only that panel shows, and the active tab turns blue; open the menu, tap Calculator — menu closes and Tools shows; tap About — the about text shows.

90-minute timing: 0–10 plan/sketch — sketch the three tabs and the menu on paper, pick colours; 10–20 demo — Rica shows a phone app with tabs and a menu; 20–65 build; 65–80 test & fix; 80–90 share — compare the old and new look side by side with Ray and Run. Test checklist: Only one panel is visible at a time; the active tab is highlighted; the menu opens and closes; all the old buttons still work after being moved. Common bug: two panels show at once — fix: showTab must set all three arrangements' Visible values every time, not just turn one on; the = "Home" comparison block does that in one line each. Success check: Gin can switch tabs, open and close the side menu, and show the same working app in a polished layout with consistent colours. Homework: Restyle one more of his apps (a game or the converter) with the same tab colours.

Session 108Advanced apps review — test all Phase 7 apps, fix and polishWed 6 Dec 2028
Wed 6 Dec 2028 | Phase 7 — Advanced Apps & Real-World Tools

Date: Wed 6 Dec 2028 | Phase: Phase 7 — Advanced Apps & Real-World Tools Learning objective: Gin can test every Phase 7 app (Sessions 91–107) systematically, list the bugs, and fix the most important ones. Components: (No new app — review day.) LabelTitle, Text "Phase 7 Review", FontSize 22; ListViewApps, Elements "Series calculator,Parallel calculator,Circuit simulator,Power calculator,Timer,Alarm,Planner,PIN lock,Converter,Maths helper,Science helper,Language helper,Budget tracker,Health tracker,Chart app,Map app,Polished UI"; LabelBug, Text "Bug list — tap an app to add a bug"; TextBoxBug, Hint "Bug: what went wrong?"; ButtonAddBug, Text "Add bug"; ListViewBugs; TinyDB1 (to save the bug list). Step-by-step build:

1) Designer setup: A simple review checklist app (or paper checklist if faster): title, ListView of the 17 Phase 7 apps, a bug TextBox + Add button, a bugs ListView, TinyDB1 to save the bug list.

2) Blocks setup: a) global variable bugList = create empty list. b) when Screen1.Initialize → set bugList to call TinyDB1.GetValue tag "phase7bugs" valueIfTagNotThere (create empty list) → set ListViewBugs.Elements to bugList. c) when ButtonAddBug.Click → if TextBoxBug.Text ≠ "" then add item (join ListViewApps.Selection + ": " + TextBoxBug.Text) to list bugList → call TinyDB1.StoreValue tag "phase7bugs" valueToStore bugList → set ListViewBugs.Elements to bugList → set TextBoxBug.Text to "". d) Then the real work, app by app in order: open each Phase 7 app on the phone with Companion, run its test checklist from its own session, tick it off or add a bug. Fix in this order: crashes first, wrong answers second, layout last. Keep a "keep / fix / drop" note per app: keep the best, fix what is close, drop what never worked.

3) Test: every Phase 7 app opens; the bug list saves and reloads; at least the top 3 bugs are fixed and re-tested before the session ends.

90-minute timing: 0–10 plan/sketch — list all 17 apps and the test order; 10–20 demo — Rica tests one app live and logs a bug; 20–65 build — test and fix round 1 (calculators + planner + converter); 65–80 test & fix — round 2 (trackers, chart, map, UI) and re-test fixes; 80–90 share — show Ray and Run the two best polished apps and the bug list. Test checklist: Each app opens without a crash; each app's own test checklist passes; the bug list is saved; fixed bugs are re-tested, not just assumed fixed. Common bug: an old app fails because a TinyDB tag was reused by a newer app — fix: rename the tag in the old app (e.g. "spending" → "budget_spending") or clear the stored value once and re-save it in the right shape. Success check: Gin can say for every Phase 7 app whether it works, what its worst bug was, and show the top fixes working. Homework: Pick his single best Phase 7 app and write two sentences about why it is the best — this feeds Capstone 2 choice next week.

Session 109Capstone 2 choice — pick final app: Electronics Lab, Smart Helper, or Game PackWed 13 Dec 2028
Wed 13 Dec 2028 | Phase 8 — Capstone & Portfolio

Date: Wed 13 Dec 2028 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can compare three capstone options and choose one final app, with reasons, before building starts. Components: LabelTitle, Text "Capstone 2 — pick your app", FontSize 22; LabelOptA, Text "A. Electronics Lab — Ohm's Law, resistor decoder, series/parallel, power, all in one lab app"; LabelOptB, Text "B. Smart Helper — chatbot + converter + planner + flashcards in one helper"; LabelOptC, Text "C. Game Pack — his 3 best games in one app with scores saved"; ButtonPickA, Text "Pick A — Electronics Lab"; ButtonPickB, Text "Pick B — Smart Helper"; ButtonPickC, Text "Pick C — Game Pack"; LabelChoice, Text "No choice yet", FontSize 18, Bold true; TextBoxWhy, Hint "Why this one? (2 sentences)"; ButtonSaveChoice, Text "Save my choice"; TinyDB1. Step-by-step build:

1) Designer setup: Title; three option labels, each with its own Pick button; a "why" TextBox; a Save button; a big choice label. Add TinyDB1 to save the choice.

2) Blocks setup: a) global variable capstoneChoice = "". b) when ButtonPickA.Click → set capstoneChoice to "Electronics Lab" → set LabelChoice.Text to "Choice: A. Electronics Lab" → set LabelOptA.TextColor to Blue (same pattern for B and C, resetting the other two labels to Black). c) when ButtonSaveChoice.Click → if capstoneChoice ≠ "" and TextBoxWhy.Text ≠ "" then → call TinyDB1.StoreValue tag "capstone2_choice" valueToStore capstoneChoice → call TinyDB1.StoreValue tag "capstone2_why" valueToStore TextBoxWhy.Text → set LabelChoice.Text to (join "Saved! Capstone 2 = " + capstoneChoice) else → set LabelChoice.Text to "Pick one and write why first". d) when Screen1.Initialize → set capstoneChoice to call TinyDB1.GetValue tag "capstone2_choice" valueIfTagNotThere "" → if capstoneChoice ≠ "" then set LabelChoice.Text to (join "Saved choice: " + capstoneChoice).

3) Test: pick each option in turn — the label and colour follow; save with no "why" — the app refuses; save properly, close and reopen — the choice is still there.

90-minute timing: 0–10 plan/sketch — write one good and one hard thing about each option; 10–20 demo — Rica re-opens his best Phase 7 apps to compare; 20–65 build — build the choice app and weigh the options (which of his old blocks can be reused?); 65–80 test & fix; 80–90 share — tell Ray, Run and Rica his choice and why, in two sentences. Test checklist: All three options are described in his own words; the choice saves and reloads; the "why" is two real sentences, not "because I like it". Common bug: the saved choice disappears after reopening — fix: Screen1.Initialize must read tag "capstone2_choice" from TinyDB1; check the tag spelling matches the StoreValue tag exactly. Success check: Gin has picked ONE capstone (Electronics Lab, Smart Helper, or Game Pack), saved it with two sentences of reasons, and can name which of his old apps he will reuse. Homework: Sketch the home screen of his chosen capstone on paper — three buttons, one per tool.

Session 110Capstone 2 plan — sketch screens, list features, cut to what fitsWed 20 Dec 2028
Wed 20 Dec 2028 | Phase 8 — Capstone & Portfolio

Date: Wed 20 Dec 2028 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can turn his Capstone 2 choice into a buildable plan: screens sketched, features listed, and the list cut to what fits in four build sessions. Components: LabelTitle, Text "Capstone 2 plan", FontSize 22; LabelChoice, Text "Capstone 2: (loaded from TinyDB)"; ListViewFeatures, Elements "Home screen,Tool 1,Tool 2,Tool 3,Save with TinyDB,Settings,Polish"; TextBoxFeature, Hint "Add a feature, e.g. Resistor decoder"; ButtonAddFeature, Text "Add feature"; ButtonCut, Text "Cut — remove selected"; LabelCount, Text "Features: 0 — aim for 3 tools + home + save"; TinyDB1. Step-by-step build:

1) Designer setup: Title; choice label at top (loaded from TinyDB); a features ListView; an add-feature TextBox + button; a cut button; a count label showing the target. Add TinyDB1. Most of this session is paper planning — the app is just the plan tracker.

2) Blocks setup: a) global variable featureList = create empty list. b) when Screen1.Initialize → set LabelChoice.Text to (join "Capstone 2: " + call TinyDB1.GetValue tag "capstone2_choice" valueIfTagNotThere "not chosen yet") → set featureList to call TinyDB1.GetValue tag "capstone2_features" valueIfTagNotThere (make a list ("Home screen", "Tool 1", "Tool 2", "Tool 3", "Save with TinyDB")) → set ListViewFeatures.Elements to featureList → call updateCount. c) procedure updateCount → set LabelCount.Text to (join length of list featureList + " features — aim for 3 tools + home + save (5 total)") → if length of list featureList > 6 then set LabelCount.TextColor to Red else set LabelCount.TextColor to Black. d) when ButtonAddFeature.Click → if TextBoxFeature.Text ≠ "" then add item TextBoxFeature.Text to list featureList → store the list under tag "capstone2_features" → set ListViewFeatures.Elements to featureList → call updateCount → set TextBoxFeature.Text to "". e) when ButtonCut.Click → if ListViewFeatures.Selection ≠ "" then remove list item (index in list featureList of ListViewFeatures.Selection) from featureList → store → refresh the ListView → call updateCount.

3) Test: the saved choice from Session 109 loads; adding and cutting features updates the count; more than 6 features turns the count red; close and reopen — the plan is still there.

90-minute timing: 0–10 plan/sketch — sketch the home screen and each tool screen on paper (the main work); 10–20 demo — Rica shows a cut list: a 9-feature plan cut to 5; 20–65 build — build the plan tracker and finalise the feature list; 65–80 test & fix; 80–90 share — present the plan to Ray and Run and ask which feature they would cut. Test checklist: Every feature maps to one build session (111, 112, 113, or 114); nothing on the list needs a component he has never used; the list is 5–6 items, not 10. Common bug: the plan list is empty after reopening — fix: the valueIfTagNotThere default list only appears the first time; if the list was stored empty once, it stays empty — re-add the five starter features and save again. Success check: Gin has a written plan: home screen + exactly 3 tools + TinyDB save, each tool named, with anything extra cut and noted as "later". Homework: Draw each tool screen on paper with its buttons and labels named, ready to build in Session 111.

Session 111Capstone 2 build 1 — home screen + first toolWed 27 Dec 2028
Wed 27 Dec 2028 | Phase 8 — Capstone & Portfolio

Date: Wed 27 Dec 2028 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can build his Capstone 2 home screen with navigation and the complete first tool, working end to end. Components: (Depends on his Session 109 choice — example below is Electronics Lab; swap the tool blocks for Smart Helper or Game Pack.) LabelTitle, Text "Electronics Lab", FontSize 22; ButtonTool1, Text "⚡ Ohm's Law"; ButtonTool2, Text "🎛 Resistor Decoder"; ButtonTool3, Text "🔋 Power Calculator"; VerticalArrangementHome, Visible true; VerticalArrangementTool1, Visible false, containing LabelV, Text "Voltage (V)"; TextBoxCurrent, Hint "Current I (A)"; TextBoxResistance, Hint "Resistance R (Ω)"; ButtonCalcV, Text "Calculate V"; LabelResultV, Text ""; ButtonBack1, Text "← Home". Step-by-step build:

1) Designer setup: Create the project (name it after his choice, e.g. "ElectronicsLab"). Home arrangement: title + three big tool buttons, each with an icon word. Tool 1 arrangement (hidden): its inputs, its calculate button, its result label, and a Back button. Use the Session 107 tab/panel pattern — one arrangement per tool, only one visible.

2) Blocks setup: a) procedure showScreen name → set VerticalArrangementHome.Visible to (name = "Home") → set VerticalArrangementTool1.Visible to (name = "Tool1") (extend when Tools 2–3 are added). b) when ButtonTool1.Click → call showScreen "Tool1". c) when ButtonBack1.Click → call showScreen "Home". d) First tool — Ohm's Law (Electronics Lab choice): when ButtonCalcV.Click → if TextBoxCurrent.Text ≠ "" and TextBoxResistance.Text ≠ "" then → set LabelResultV.Text to (join "V = " + (TextBoxCurrent.Text × TextBoxResistance.Text) + " V") else → set LabelResultV.Text to "Enter I and R first". (Smart Helper choice: first tool = converter, reuse Session 99 blocks. Game Pack choice: first tool = his best game, reuse its blocks.) e) when Screen1.Initialize → call showScreen "Home".

3) Test: open the app — home shows, no tool panel visible; tap Tool 1 — its screen shows; calculate 2 A × 10 Ω = 20 V; tap Back — home returns.

90-minute timing: 0–10 plan/sketch — check the Session 110 paper sketch for Tool 1; 10–20 demo — Rica opens a finished multi-tool app and navigates it; 20–65 build; 65–80 test & fix; 80–90 share — demo home + Tool 1 to Ray and Run. Test checklist: Home shows on open; only one panel visible at a time; Tool 1 gives the right answer for a known input (2 × 10 = 20); Back always returns home. Common bug: Tool 1's panel shows on top of the home screen — fix: showScreen must set every arrangement's Visible in one procedure; a panel left Visible true from the Designer will stay on top. Success check: Gin has a working home screen and one complete, tested tool — the capstone already does something useful. Homework: Write down exactly what Tool 2 will be (name + its inputs + its answer) so Session 112 starts with building, not deciding.

Session 112Capstone 2 build 2 — second tool / featureWed 3 Jan 2029
Wed 3 Jan 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 3 Jan 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can add the second tool to his Capstone 2 app, reusing blocks from his earlier app for that tool. Components: Add to the Session 111 project: VerticalArrangementTool2, Visible false, containing — for Electronics Lab: SpinnerBand1, SpinnerBand2, SpinnerBand3 (Elements "Black,Brown,Red,Orange,Yellow,Green,Blue,Violet,Grey,White"), ButtonDecode, Text "Decode resistor", LabelResistor, Text ""; for Smart Helper: the chatbot TextBox + ButtonAsk + LabelReply (reuse Session 77–79); for Game Pack: the second game's Canvas + score Label + start Button (reuse his game blocks). ButtonTool2 on the home screen must already exist from Session 111 — wire it up now. Step-by-step build:

1) Designer setup: Add the Tool 2 arrangement to the same project; keep it hidden. Add its inputs and result label. Do not change the home screen layout — only wire ButtonTool2.

2) Blocks setup: a) Extend showScreen with set VerticalArrangementTool2.Visible to (name = "Tool2") and add the false lines for the other panels. b) when ButtonTool2.Click → call showScreen "Tool2"; add a Back button in Tool 2: when ButtonBack2.Click → call showScreen "Home". c) Second tool — resistor decoder (Electronics Lab choice): reuse Session 4 blocks: global list colourValues = make a list (0, 1, 2, 3, 4, 5, 6, 7, 8, 9) matching the Spinner order; when ButtonDecode.Click → set global d1 to index in list colourValues of (SpinnerBand1.Selection) — simpler: set d1 to SpinnerBand1.SelectionIndex − 1, d2 the same from Band 2, multiplier from Band 3 → set LabelResistor.Text to (join (d1 × 10 + d2) × (10 ^ multiplier) + " Ω") — example: Brown (1), Black (0), Red (×100) → 1000 Ω. (Smart Helper: chatbot keyword blocks; Game Pack: second game blocks — same pattern, copy the working blocks from the original project, then rename components to match.) d) Re-test Tool 1 after the change — nothing in Tool 1 may break.

3) Test: home → Tool 2 → decode Brown-Black-Red = 1000 Ω; Back → home; Tool 1 still gives 2 × 10 = 20 V.

90-minute timing: 0–10 plan/sketch — check the paper sketch for Tool 2; 10–20 demo — Rica decodes one resistor by hand, then in the old app; 20–65 build; 65–80 test & fix; 80–90 share — demo both tools back to back to Ray and Run. Test checklist: Tool 2's answer is right for two known resistors; Tool 1 still works; only one panel shows at a time; Back works from Tool 2. Common bug: the decoder gives 10× the right answer — fix: check the multiplier: Band 3 Red means ×100 (10^2), so use SelectionIndex − 1 as the exponent, and confirm Black = 0, Brown = 1 in the Spinner order. Success check: Gin has two working tools in one app, with the second built by reusing his own earlier blocks. Homework: Write down Tool 3 (name + inputs + answer) for Session 113.

Session 113Capstone 2 build 3 — third tool / featureWed 10 Jan 2029
Wed 10 Jan 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 10 Jan 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can add the third and final tool to his Capstone 2 app, so all three tools work from one home screen. Components: Add to the same project: VerticalArrangementTool3, Visible false, containing — for Electronics Lab: TextBoxVoltage3, Hint "Voltage V"; TextBoxCurrent3, Hint "Current I (A)"; ButtonCalcP, Text "Calculate power"; LabelResultP, Text ""; for Smart Helper: planner or flashcards (reuse Session 97 or 102); for Game Pack: the third game (reuse its blocks). ButtonTool3 on the home screen, wired up now; ButtonBack3, Text "← Home". Step-by-step build:

1) Designer setup: Add the Tool 3 arrangement, hidden. Add its inputs, calculate button, result label, Back button. Keep the same colours and button sizes as Tools 1–2 so the app looks like one app.

2) Blocks setup: a) Extend showScreen with set VerticalArrangementTool3.Visible to (name = "Tool3") and false lines for every other panel. b) when ButtonTool3.Click → call showScreen "Tool3"; when ButtonBack3.Click → call showScreen "Home". c) Third tool — power calculator (Electronics Lab choice): when ButtonCalcP.Click → if TextBoxVoltage3.Text ≠ "" and TextBoxCurrent3.Text ≠ "" then → set LabelResultP.Text to (join "P = " + (TextBoxVoltage3.Text × TextBoxCurrent3.Text) + " W") else → set LabelResultP.Text to "Enter V and I first" — example: 12 V × 2 A = 24 W. (Smart Helper: planner/flashcard blocks; Game Pack: third game blocks — copy from the original project, rename components to match.) d) Full pass: open the app, visit Home → Tool 1 → Home → Tool 2 → Home → Tool 3 → Home, checking each answer.

3) Test: 12 V × 2 A = 24 W in Tool 3; Tools 1 and 2 still give their known answers; no panel overlaps another.

90-minute timing: 0–10 plan/sketch — check the paper sketch for Tool 3; 10–20 demo — Rica calculates one power value by hand; 20–65 build; 65–80 test & fix; 80–90 share — demo all three tools in a row to Ray and Run, one minute each. Test checklist: All three tools give right answers for known inputs; only one panel visible at a time; every Back button returns home; the three tools look consistent (same colours, sizes). Common bug: Tool 3's answer appears in Tool 1's result label — fix: copied blocks still point at the old label; rename the result label in the copied blocks to LabelResultP (or the Tool 3 label) and re-test. Success check: Gin has a complete three-tool capstone app working from one home screen. Homework: List two things to save with TinyDB next session (e.g. last answers, favourite tool, settings) and one setting he wants (e.g. sound on/off).

Session 114Capstone 2 data — save with TinyDB, settingsWed 17 Jan 2029
Wed 17 Jan 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 17 Jan 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can add TinyDB saving and a settings screen to his Capstone 2 app, so last results and settings survive closing the app. Components: Add to the same project: TinyDB1; ButtonSettings, Text "⚙ Settings" (on home); VerticalArrangementSettings, Visible false, containing LabelSettingsTitle, Text "Settings"; SpinnerTheme, Elements "Light,Dark"; ButtonSound, Text "Sound: ON"; ButtonBackSettings, Text "← Home"; LabelLast, Text "Last result: —" (on home, shows the last saved answer). Step-by-step build:

1) Designer setup: Add a Settings button to the home screen; add the hidden Settings arrangement with a theme Spinner, a sound toggle button, and a Back button. Add TinyDB1 and a "Last result" label on the home screen.

2) Blocks setup: a) Extend showScreen with the Settings panel. b) Save the last result: in each tool's calculate block, after setting the result label, add call TinyDB1.StoreValue tag "last_result" valueToStore LabelResult.Text (use one tag, or one per tool: "last_v", "last_resistor", "last_p"). c) when Screen1.Initialize → set LabelLast.Text to (join "Last result: " + call TinyDB1.GetValue tag "last_result" valueIfTagNotThere "—") → set SpinnerTheme.Selection to call TinyDB1.GetValue tag "theme" valueIfTagNotThere "Light" → call applyTheme. d) procedure applyTheme → if SpinnerTheme.Selection = "Dark" then set Screen1.BackgroundColor to Black, LabelTitle.TextColor to White else set Screen1.BackgroundColor to White, LabelTitle.TextColor to Black. e) when SpinnerTheme.AfterSelecting → call TinyDB1.StoreValue tag "theme" valueToStore SpinnerTheme.Selection → call applyTheme. f) Global variable soundOn = true; when ButtonSound.Click → set soundOn to (not soundOn) → if soundOn then set ButtonSound.Text to "Sound: ON" else set ButtonSound.Text to "Sound: OFF" → call TinyDB1.StoreValue tag "sound" valueToStore soundOn. g) when Screen1.Initialize also loads it: set soundOn to call TinyDB1.GetValue tag "sound" valueIfTagNotThere true → set ButtonSound.Text accordingly.

3) Test: calculate an answer, close and reopen — the last result shows on home; switch to Dark, close and reopen — still Dark; turn sound off, close and reopen — still OFF.

90-minute timing: 0–10 plan/sketch — list what to save (last result, theme, sound); 10–20 demo — Rica shows a settings screen in a phone app; 20–65 build; 65–80 test & fix; 80–90 share — show Ray and Run the Dark theme and the saved last result. Test checklist: Last result reloads; theme reloads; sound setting reloads; settings Back returns home; no tool broke when the save blocks were added. Common bug: the theme loads but the labels stay black on a black background — fix: applyTheme must set the TextColor of every title and result label, not just the screen background; set them all in the one procedure. Success check: Gin can close the app and reopen it to find his last result, theme, and sound setting exactly as he left them. Homework: Write the bug list for Session 115: use the app for 10 minutes and note anything odd, slow, or confusing.

Session 115Capstone 2 test 1 — playtest, list bugsWed 24 Jan 2029
Wed 24 Jan 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 24 Jan 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can playtest his whole Capstone 2 app like a user, find the bugs, and write them down in order of importance. Components: (No new building — testing day.) LabelTitle, Text "Capstone 2 playtest", FontSize 22; ListViewBugs, Elements empty; TextBoxBug, Hint "Bug: what happened, where?"; SpinnerSeverity, Elements "Crash,Wrong answer,Confusing,Small polish"; ButtonAddBug, Text "Add bug"; LabelBugCount, Text "Bugs found: 0"; TinyDB1 (save the bug list under tag "capstone2_bugs"). Step-by-step build:

1) Designer setup: A simple bug-log app (or paper list): title, bug TextBox, severity Spinner, Add button, bugs ListView, count label. Add TinyDB1.

2) Blocks setup: a) global variable bugList = create empty list. b) when Screen1.Initialize → set bugList to call TinyDB1.GetValue tag "capstone2_bugs" valueIfTagNotThere (create empty list) → set ListViewBugs.Elements to bugList → call updateCount. c) when ButtonAddBug.Click → if TextBoxBug.Text ≠ "" then add item (join SpinnerSeverity.Selection + ": " + TextBoxBug.Text) to list bugList → call TinyDB1.StoreValue tag "capstone2_bugs" valueToStore bugList → set ListViewBugs.Elements to bugList → call updateCount → set TextBoxBug.Text to "". d) procedure updateCount → set LabelBugCount.Text to (join "Bugs found: " + length of list bugList). e) The playtest itself — run through this script on the phone: open the app fresh; use Tool 1 with a normal input, an empty input, and a silly input (letters, 0); do the same for Tools 2 and 3; switch theme to Dark and back; turn sound off and on; close and reopen and check the last result; hand the phone to Ray or Run with no instructions and watch where they get stuck — every stuck moment is a bug.

3) Test: the bug list saves and reloads; every bug has a severity; at least one bug is found by Ray/Run, not just by Gin.

90-minute timing: 0–10 plan/sketch — write the playtest script on paper; 10–20 demo — Rica playtests Tool 1 live and logs one bug; 20–65 build — playtest round 1 (Gin, all three tools + settings); 65–80 test & fix — playtest round 2 (Ray and Run try it with no help) and log what they find; 80–90 share — read the bug list aloud, sorted by severity. Test checklist: Every tool tested with empty input and with letters; settings tested both ways; a fresh user (Ray/Run) tried it without help; the bug list is saved. Common bug: typing letters into a number box gives a blank result or a crash — fix (for next session): check TextBox.Text ≠ "" and use an is a number? test before calculating, and show "Enter numbers only" if it fails. Success check: Gin has a saved, severity-sorted bug list with at least 5 real bugs, including one found by someone else. Homework: Rank the bug list: circle the 3 bugs to fix first in Session 116 and cross out any that are "later, not now".

Session 116Capstone 2 fix — fix bugs, polish layoutWed 31 Jan 2029
Wed 31 Jan 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 31 Jan 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can fix the top bugs from his Session 115 list, re-test each fix, and polish the layout so the app looks finished. Components: (Same Capstone 2 project — no new screens.) Existing components only, plus: LabelBugFix, Text "Fixing: (top bug)"; ButtonMarkFixed, Text "Mark fixed"; ListViewBugs (loaded from TinyDB1 tag "capstone2_bugs"); global variable fixedCount = 0. Step-by-step build:

1) Designer setup: No new screens. Open the bug list from Session 115 (TinyDB tag "capstone2_bugs") and work from the top: crashes first, wrong answers second, confusing layout third, small polish last.

2) Blocks setup: a) Fix the common bugs in order: (1) Empty/letter input crash — in each calculate block, wrap the maths in if (TextBox.Text ≠ "") and (is a number? TextBox.Text) then → calculate else → set LabelResult.Text to "Enter numbers only"; (2) Wrong answer — re-check one known answer per tool (2 A × 10 Ω = 20 V; Brown-Black-Red = 1000 Ω; 12 V × 2 A = 24 W) and fix the block order; (3) Dark theme labels unreadable — add the missing TextColor lines in applyTheme; (4) Two panels visible — check showScreen sets every arrangement. b) Polish: make all buttons the same height (e.g. 50 pixels) and the same accent colour; make result labels FontSize 20, Bold true; add one space or divider between sections; check the layout on the real phone, not just the Designer — text that fits on the computer screen may overflow on the phone. c) when ButtonMarkFixed.Click → set fixedCount to fixedCount + 1 → set LabelBugFix.Text to (join fixedCount + " bugs fixed — re-test each one!").

3) Test: after EACH fix, run that tool's known-answer test again before moving on; close and reopen once at the end and run the full playtest script from Session 115 quickly.

90-minute timing: 0–10 plan/sketch — read the ranked bug list, pick the top 3; 10–20 demo — Rica fixes one bug live and re-tests it; 20–65 build — fix round 1 (crashes + wrong answers); 65–80 test & fix — fix round 2 (layout + polish) and full re-test; 80–90 share — show Ray and Run the before/after: the same bug, now fixed. Test checklist: Every fixed bug is re-tested and passes; no new bug appeared while fixing (run all three known answers at the end); the layout looks tidy on the phone; the bug list is updated — fixed bugs noted, not deleted. Common bug: fixing one tool breaks another — fix: this usually means a copied block still points at the wrong label or TextBox; after every fix, run the other two tools' known answers before calling it done. Success check: Gin can show the top 3 bugs fixed and re-tested, with all three tools still giving right answers and a tidy layout. Homework: Choose Capstone 3: it must be a DIFFERENT type from Capstone 2 (if Capstone 2 was Electronics Lab, Capstone 3 is Smart Helper or Game Pack) — write one sentence for why.

Session 117Capstone 3 choice — second large app, different type from Capstone 2Wed 7 Feb 2029
Wed 7 Feb 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 7 Feb 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can choose a second capstone of a different type from Capstone 2, with reasons, and name what he will reuse and what is new. Components: LabelTitle, Text "Capstone 3 — pick a different app", FontSize 22; LabelCap2, Text "Capstone 2 was: (loaded from TinyDB)"; LabelOptA, Text "A. Smart Helper — chatbot + converter + planner + flashcards"; LabelOptB, Text "B. Game Pack — 3 best games, scores saved"; LabelOptC, Text "C. Electronics Lab — Ohm's Law, decoder, series/parallel, power"; ButtonPickA, Text "Pick A"; ButtonPickB, Text "Pick B"; ButtonPickC, Text "Pick C"; LabelChoice, Text "No choice yet", FontSize 18, Bold true; TextBoxWhy, Hint "Why this one? How is it different from Capstone 2?"; ButtonSaveChoice, Text "Save my choice"; TinyDB1. Step-by-step build:

1) Designer setup: Title; a label showing the saved Capstone 2 choice (loaded from TinyDB tag "capstone2_choice"); three option labels with Pick buttons; a "why + how is it different" TextBox; Save button; choice label. Add TinyDB1.

2) Blocks setup: a) global variable capstone3Choice = "". b) when Screen1.Initialize → set LabelCap2.Text to (join "Capstone 2 was: " + call TinyDB1.GetValue tag "capstone2_choice" valueIfTagNotThere "?") → set capstone3Choice to call TinyDB1.GetValue tag "capstone3_choice" valueIfTagNotThere "". c) when ButtonPickA.Click → set capstone3Choice to "Smart Helper" → set LabelChoice.Text to "Choice: A. Smart Helper" (same for B and C). d) when ButtonSaveChoice.Click → if capstone3Choice ≠ "" and TextBoxWhy.Text ≠ "" then → if capstone3Choice = call TinyDB1.GetValue tag "capstone2_choice" valueIfTagNotThere "" then set LabelChoice.Text to "That is the same as Capstone 2 — pick a different type!" else → call TinyDB1.StoreValue tag "capstone3_choice" valueToStore capstone3Choice → call TinyDB1.StoreValue tag "capstone3_why" valueToStore TextBoxWhy.Text → set LabelChoice.Text to (join "Saved! Capstone 3 = " + capstone3Choice) else → set LabelChoice.Text to "Pick one and write why first".

3) Test: try saving the same type as Capstone 2 — the app refuses; save a different type with a reason — it saves; close and reopen — the choice is still there.

90-minute timing: 0–10 plan/sketch — write one good and one hard thing about each option, and what is new in it; 10–20 demo — Rica compares Capstone 2 with the two other types; 20–65 build — build the choice app and decide the choice; 65–80 test & fix; 80–90 share — tell Ray, Run and Rica the choice and how it differs from Capstone 2. Test checklist: The choice is a different type from Capstone 2 (the app itself blocks the same choice); the reason mentions the difference; the choice saves and reloads. Common bug: the "same as Capstone 2" check never triggers — fix: compare capstone3Choice with the value read from tag "capstone2_choice" at save time, not with a label's text; check the tag spelling matches Session 109 exactly. Success check: Gin has picked a Capstone 3 of a different type, saved with a reason that names the difference, and can list one thing he will reuse and one thing that is new. Homework: Sketch the Capstone 3 home screen on paper — home + first feature, named.

Session 118Capstone 3 build 1 — home + first featureWed 14 Feb 2029
Wed 14 Feb 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 14 Feb 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can build his Capstone 3 home screen with navigation and the complete first feature, working end to end. Components: (New project, named after his Session 117 choice — example below is Game Pack; swap for Smart Helper or Electronics Lab.) LabelTitle, Text "Game Pack", FontSize 22; ButtonGame1, Text "🎮 Reaction Game"; ButtonGame2, Text "🧠 Memory Game"; ButtonGame3, Text "🎲 Dice Roller"; VerticalArrangementHome, Visible true; VerticalArrangementGame1, Visible false, containing Canvas1 (game area), ButtonStart1, Text "Start", LabelScore1, Text "Score: 0", LabelBest1, Text "Best: 0"; ButtonBack1, Text "← Home"; TinyDB1 (for best score). Step-by-step build:

1) Designer setup: New project named after the choice. Home arrangement: title + three big game/feature buttons. Feature 1 arrangement (hidden): its play area, start button, score label, best label, Back button. Use the Session 107/111 panel pattern — one arrangement per feature, only one visible.

2) Blocks setup: a) procedure showScreen name → set VerticalArrangementHome.Visible to (name = "Home") → set VerticalArrangementGame1.Visible to (name = "Game1") (extend in later sessions). b) when ButtonGame1.Click → call showScreen "Game1"; when ButtonBack1.Click → call showScreen "Home". c) First feature — reaction game (Game Pack choice; reuse Session 9 blocks): global variables score = 0, best = 0, waiting = false; Clock1, TimerInterval 1000; when ButtonStart1.Click → set LabelScore1.Text to "Wait for green…" → set Canvas1.BackgroundColor to Red → set waiting to true → call Clock1.TimerEnabled to true — use a random delay: set Clock1.TimerInterval to random integer from 1000 to 3000. d) when Clock1.Timer → if waiting then set Canvas1.BackgroundColor to Green → set waiting to false → set global startTime to Clock1.Now (or use a counter variable) → call Clock1.TimerEnabled to false. e) when Canvas1.Touched → if Canvas1.BackgroundColor = Green then → set score to score + 1 → set LabelScore1.Text to (join "Score: " + score) → if score > best then set best to score, call TinyDB1.StoreValue tag "game1_best" valueToStore best → set LabelBest1.Text to (join "Best: " + best) → set Canvas1.BackgroundColor to Red else if waiting then set LabelScore1.Text to "Too soon! Wait for green.". f) when Screen1.Initialize → set best to call TinyDB1.GetValue tag "game1_best" valueIfTagNotThere 0 → set LabelBest1.Text to (join "Best: " + best) → call showScreen "Home". (Smart Helper choice: first feature = chatbot, reuse Sessions 77–79; Electronics Lab choice: first feature = series calculator, reuse Session 91.)

3) Test: open — home shows; tap Game 1 — game screen shows; tap Start, wait for green, tap fast — score goes up and best saves; tap too soon — "Too soon!" and no point; close and reopen — best is still there.

90-minute timing: 0–10 plan/sketch — check the Session 117 paper sketch for Feature 1; 10–20 demo — Rica plays one round of the old reaction game; 20–65 build; 65–80 test & fix; 80–90 share — challenge Ray and Run to beat his score. Test checklist: Home shows on open; only one panel visible; the game scores only on green, not on red; best score survives closing the app. Common bug: tapping during red still scores — fix: the Canvas Touched block must check BackgroundColor = Green first; a tap while waiting (red) must only show "Too soon!" and never add to the score. Success check: Gin has a working Capstone 3 home screen and one complete, tested feature. Homework: Write down Feature 2 (name + what it does + what it saves) for Session 119.

Session 119Capstone 3 build 2 — second feature + dataWed 21 Feb 2029
Wed 21 Feb 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 21 Feb 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can add the second feature to Capstone 3 and save its data with TinyDB, so progress is kept between sessions. Components: Add to the Capstone 3 project: VerticalArrangementGame2, Visible false, containing — for Game Pack: a memory game grid (ButtonCard1 … ButtonCard8, each Text "?"), LabelPairs, Text "Pairs found: 0 / 4", ButtonShuffle2, Text "Shuffle cards"; for Smart Helper: planner (reuse Session 97); for Electronics Lab: resistor decoder (reuse Session 4). TinyDB1 already in the project — add tags "game2_best" / "capstone3_data". ButtonGame2 on home, wired up now; ButtonBack2, Text "← Home". Step-by-step build:

1) Designer setup: Add the Feature 2 arrangement, hidden. Add its buttons/labels. Do not change the home layout — only wire ButtonGame2.

2) Blocks setup: a) Extend showScreen with set VerticalArrangementGame2.Visible to (name = "Game2") and false lines for the other panels. b) when ButtonGame2.Click → call showScreen "Game2"; when ButtonBack2.Click → call showScreen "Home". c) Second feature — memory game (Game Pack choice; reuse Session 11 blocks): global list cards = make a list ("⚡", "⚡", "🔋", "🔋", "🎛", "🎛", "💡", "💡"); global variables firstPick = 0, pairsFound = 0; procedure shuffleCards → set cards to (shuffle list cards) — App Inventor has no shuffle block, so build it: for each number i from 1 to 8 → set j to random integer from 1 to 8 → swap list items i and j (use a temporary variable). d) when ButtonCard1.Click → call flipCard 1 — procedure flipCard n → set Button (by n) .Text to select list item cards index n → if firstPick = 0 then set firstPick to n else if select list item cards index firstPick = select list item cards index n then → set pairsFound to pairsFound + 1 → set LabelPairs.Text to (join "Pairs found: " + pairsFound + " / 4") → set firstPick to 0 → if pairsFound = 4 then set LabelPairs.Text to "You win! All 4 pairs!" → call TinyDB1.StoreValue tag "game2_wins" valueToStore (call TinyDB1.GetValue tag "game2_wins" valueIfTagNotThere 0 + 1) else → (after a short Clock delay) set both cards' Text back to "?" → set firstPick to 0. e) Re-test Feature 1 after the change.

3) Test: flip two matching cards — they stay face-up and pairs goes up; flip two different cards — they flip back; finish all 4 pairs — "You win!" and the win count saves; Feature 1 still scores correctly.

90-minute timing: 0–10 plan/sketch — check the paper sketch for Feature 2 and its data; 10–20 demo — Rica plays one memory round in the old app; 20–65 build; 65–80 test & fix; 80–90 share — let Ray and Run play Feature 2 and try to beat his pairs. Test checklist: Matching pairs stay up; non-matching pairs flip back; the win count saves and reloads; Feature 1 still works; only one panel shows at a time. Common bug: the same card tapped twice counts as a pair — fix: in flipCard, if n = firstPick then do nothing and return; a pair needs two different cards. Success check: Gin has two working features in Capstone 3, with the second one's data (wins/best) saved in TinyDB. Homework: Write down Feature 3 (name + which sensor, AI, or connectivity piece it uses) for Session 120.

Session 120Capstone 3 build 3 — sensors / AI / connectivity featureWed 28 Feb 2029
Wed 28 Feb 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 28 Feb 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can add a third feature to Capstone 3 that uses a sensor, AI, or connectivity — the new piece this capstone adds. Components: Add to the Capstone 3 project: VerticalArrangementGame3, Visible false, containing — for Game Pack: a tilt game (AccelerometerSensor1; Canvas1 with a Ball sprite; LabelTilt, Text "Tilt to move the ball"); for Smart Helper: a voice helper (SpeechRecognizer1, TextToSpeech1, ButtonListen, Text "🎤 Speak", LabelHeard, Text ""); for Electronics Lab: a Bluetooth remote (BluetoothClient1, ButtonSend, Text "Send to micro:bit", LabelReply, Text ""). ButtonGame3 on home, wired up now; ButtonBack3, Text "← Home". Step-by-step build:

1) Designer setup: Add the Feature 3 arrangement, hidden. Add the sensor/AI/connectivity component (non-visible where needed) and its labels/buttons. This feature is device-dependent — test on the real phone with Companion, not only in the emulator.

2) Blocks setup: a) Extend showScreen with set VerticalArrangementGame3.Visible to (name = "Game3") and false lines for every other panel. b) when ButtonGame3.Click → call showScreen "Game3"; when ButtonBack3.Click → call showScreen "Home". c) Third feature — tilt game (Game Pack choice; reuse Sessions 41–42): when AccelerometerSensor1.AccelerationChanged → set LabelTilt.Text to (join "X: " + xAccel + " Y: " + yAccel) → set Ball.X to Ball.X + (xAccel × 2) → set Ball.Y to Ball.Y + (yAccel × 2) → if Ball hits the Canvas edge then set LabelTilt.Text to "Out! Tap Start to try again". Add a target: if Ball collides with the target sprite then set LabelTilt.Text to "You reached the target!". (Smart Helper choice: when ButtonListen.Click → call SpeechRecognizer1.GetText → when SpeechRecognizer1.AfterGettingText → set LabelHeard.Text to result → if result contains "ohm" then call TextToSpeech1.Speak message "Ohm's Law: V equals I times R" else call TextToSpeech1.Speak message "I heard: " + result. Electronics Lab choice: when ButtonSend.Click → if BluetoothClient1.IsConnected then call BluetoothClient1.SendText text "HELLO" else set LabelReply.Text to "Not connected — pair the micro:bit first"; when BluetoothClient1.DataReceived → set LabelReply.Text to message.) d) Full pass: Home → Feature 1 → Home → Feature 2 → Home → Feature 3 → Home.

3) Test: tilt the phone — the ball moves the right way; reach the target — the win message shows; Features 1 and 2 still work; if the sensor/device is not available, note it plainly and use the fallback (buttons to move the ball instead of tilt).

90-minute timing: 0–10 plan/sketch — check the paper sketch for Feature 3 and its fallback; 10–20 demo — Rica tilts the phone and the ball moves; 20–65 build; 65–80 test & fix; 80–90 share — let Ray and Run try the tilt/speak/Bluetooth feature. Test checklist: The sensor/AI/connectivity feature responds on the real phone; Features 1 and 2 still work; only one panel shows; if the device is missing, the fallback (buttons) works and the gap is written down, not hidden. Common bug: the ball moves the wrong way or too fast — fix: swap the sign (xAccel × −2) or lower the multiplier to ×1; test by tilting slowly and watching which way the ball goes. Success check: Gin has a complete three-feature Capstone 3, with the third feature using a sensor, AI, or connectivity piece (or a written-down fallback if the device was not available). Homework: Playtest all three features for 10 minutes and write the bug list for Session 121.

Session 121Capstone 3 test & fix — full playtest, fix bugsWed 7 Mar 2029
Wed 7 Mar 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 7 Mar 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can run a full playtest of Capstone 3, fix the bugs he finds, and re-test every fix. Components: (Same Capstone 3 project — no new screens.) ListViewBugs; TextBoxBug, Hint "Bug: what happened, where?"; SpinnerSeverity, Elements "Crash,Wrong answer,Confusing,Small polish"; ButtonAddBug, Text "Add bug"; ButtonMarkFixed, Text "Mark fixed"; LabelBugCount, Text "Bugs found: 0"; TinyDB1 (tag "capstone3_bugs"); global variable fixedCount = 0. Step-by-step build:

1) Designer setup: Reuse the Session 115 bug-log pattern in the Capstone 3 project (or on paper): bug TextBox, severity Spinner, Add button, bugs ListView, count label. Load the saved list from TinyDB tag "capstone3_bugs".

2) Blocks setup: a) Same bug-log blocks as Session 115, with tag "capstone3_bugs". b) Playtest script, all three features: open fresh; Feature 1 with normal, empty, and silly input; Feature 2 to a full win and a full loss; Feature 3 on the real phone (tilt / speak / Bluetooth) and with the fallback; switch panels quickly five times; close and reopen and check saved data; hand the phone to Ray or Run with no instructions and watch where they get stuck. c) Fix in severity order: crashes first (empty/letter input guards — if TextBox.Text ≠ "" and is a number? before calculating), wrong answers second (re-check one known answer per feature), confusing layout third, polish last. d) After EACH fix, re-test that feature before moving on; when ButtonMarkFixed.Click → set fixedCount to fixedCount + 1 → set LabelBugCount.Text to (join fixedCount + " fixed of " + length of list bugList).

3) Test: every fixed bug passes its re-test; all three features give their known answers at the end; saved data survives closing the app; at least one bug was found by Ray/Run.

90-minute timing: 0–10 plan/sketch — write the playtest script from the Session 120 homework bug list; 10–20 demo — Rica playtests Feature 3 live and logs one bug; 20–65 build — playtest + fix round 1 (crashes + wrong answers); 65–80 test & fix — fix round 2 (layout + polish) and full re-test; 80–90 share — show Ray and Run the worst bug and its fix. Test checklist: The bug list is saved; every fix is re-tested, not assumed; no fix broke another feature (run all three known answers at the end); the app works on the real phone, not just the emulator. Common bug: a fix for Feature 2 breaks Feature 1 — fix: copied blocks still point at the wrong component; after every fix, run the other features' known answers before calling it done. Success check: Gin can show a saved bug list, the top bugs fixed and re-tested, and all three Capstone 3 features working. Homework: Pick his best app overall (Capstone 2, Capstone 3, or one Phase 7 app) and write two sentences about why — this is the lead app for the portfolio in Session 122.

Session 122Portfolio app — one app that links all his best appsWed 14 Mar 2029
Wed 14 Mar 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 14 Mar 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can build a portfolio app that presents his best apps in one place, with a name, a short description, and a way to open each one. Components: LabelTitle, Text "Gin's App Portfolio", FontSize 22; ListViewApps, Elements "Electronics Lab (Capstone 2),Smart Helper / Game Pack (Capstone 3),Unit Converter,Maths Helper,Chart Maker,Health Tracker"; LabelDesc, Text "Tap an app to see what it does", FontSize 16; ButtonOpen, Text "Open this app"; ButtonAbout, Text "About me"; LabelAbout, Text "Hi! I'm Gin. I build apps with MIT App Inventor — calculators, games, and helpers. My favourite tool is Ohm's Law: V = I × R.", Visible false. Step-by-step build:

1) Designer setup: Title; a ListView of his best apps (5–6, chosen from Capstones 2–3 and Phase 7); a description label; an Open button; an About button and a hidden about label. Keep it clean — this app is the shop window for everything else.

2) Blocks setup: a) global lists: appNames = the ListView elements; appDescs = make a list ("Three electronics tools: Ohm's Law, resistor decoder, power — my Capstone 2.", "My second big app — games / helper with saved scores.", "Convert length, mass, temperature and electronics units.", "Fractions, percentages and averages with working shown.", "Type numbers, get a labelled bar chart.", "Log water and exercise, see the week as a chart.") — write the real descriptions for his actual apps on the day. b) when ListViewApps.AfterPicking → set global i to index in list appNames of ListViewApps.Selection → set LabelDesc.Text to select list item appDescs index i. c) when ButtonOpen.Click → if ListViewApps.Selection ≠ "" then → open another screen (or, since each app is a separate .aia project, show how to open it: set LabelDesc.Text to (join "Open the project '" + ListViewApps.Selection + "' in App Inventor — tap the project name") — be honest in the app: separate .aia projects cannot be opened from inside one app, so the portfolio links by name and description, and each app is opened from the App Inventor project list; do not pretend the button launches the other app. A better honest build: make the Open button open another screen to a detail screen inside the portfolio app that shows the app's screenshot description and its best feature. d) when ButtonAbout.Click → set LabelAbout.Visible to (not LabelAbout.Visible).

3) Test: tap each app in the list — the right description shows; tap About — the about text appears and hides again; the list has 5–6 apps, no duplicates, no broken names.

90-minute timing: 0–10 plan/sketch — pick the 5–6 best apps and write one-line descriptions; 10–20 demo — Rica shows a simple portfolio page; 20–65 build; 65–80 test & fix; 80–90 share — walk Ray and Run through the portfolio list and ask which app they would open first. Test checklist: Every list item shows its matching description (same-index lists); About toggles; no app name appears twice; the Open button is honest about what it does (it does not claim to launch a separate .aia). Common bug: descriptions are off by one — fix: the names list and the descriptions list must stay in the same order; the index comes from the names list and is used on the descriptions list. Success check: Gin has a portfolio app listing 5–6 of his best apps with a correct one-line description each and an About section. Homework: For each portfolio app, write one sentence: what it does and who it is for.

Session 123Portfolio polish — icons, names, screenshots, descriptionsWed 21 Mar 2029
Wed 21 Mar 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 21 Mar 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can polish his portfolio app with clear names, short descriptions, and screenshots, so a stranger can understand each app in seconds. Components: (Same portfolio app from Session 122.) Image1 … Image3 (or one Image per app on its detail screen), Picture set to a screenshot file; LabelAppName, Text "App name", FontSize 20, Bold true; LabelAppDesc, Text "What it does, who it is for", FontSize 16; ButtonPrev, Text "← Previous app"; ButtonNext, Text "Next app →"; LabelPage, Text "1 of 6". Step-by-step build:

1) Designer setup: Add a detail view to the portfolio app: an Image at the top, the app name, its description, Previous/Next buttons, and a page label. Take screenshots of each app on the phone (Companion → screenshot, or the phone's own screenshot) and upload them as media in the project.

2) Blocks setup: a) global lists: appNames, appDescs (from Session 122), appShots = make a list ("shot_lab.png", "shot_helper.png", "shot_converter.png", "shot_maths.png", "shot_chart.png", "shot_health.png") — use the real uploaded file names; global variable pageIndex = 1. b) procedure showPage → set LabelAppName.Text to select list item appNames index pageIndex → set LabelAppDesc.Text to select list item appDescs index pageIndex → set Image1.Picture to select list item appShots index pageIndex → set LabelPage.Text to (join pageIndex + " of " + length of list appNames). c) when Screen1.Initialize → call showPage. d) when ButtonNext.Click → set pageIndex to pageIndex + 1 → if pageIndex > length of list appNames then set pageIndex to 1 → call showPage. e) when ButtonPrev.Click → set pageIndex to pageIndex − 1 → if pageIndex < 1 then set pageIndex to length of list appNames → call showPage. f) Polish pass: shorten every description to one or two sentences; rename any confusing app name; make all titles the same size and colour; check the screenshots are the right way up and readable.

3) Test: Next past the last app wraps to the first; Previous from the first wraps to the last; every page shows the right name, description, and screenshot together; all screenshots are readable on the phone.

90-minute timing: 0–10 plan/sketch — list the 6 apps and what each screenshot must show; 10–20 demo — Rica shows a good and a bad app description; 20–65 build — take screenshots, upload, wire the pages; 65–80 test & fix; 80–90 share — flip through the portfolio with Ray and Run and ask what is still confusing. Test checklist: Name, description, and screenshot always match on every page; Next/Previous wrap around; no screenshot is sideways or blank; every description is two sentences or fewer. Common bug: the screenshot shows the wrong app — fix: the three lists (names, descriptions, screenshots) must stay in the same order, and pageIndex is the only index used for all three. Success check: Gin can flip through a polished portfolio where every app has a clear name, a short description, and a matching screenshot. Homework: Practise the 2-minute talk for his lead app (Session 124): what it does, how he built it, one hard bug he fixed.

Session 124Showcase rehearsal — present each app in 2 minutesWed 28 Mar 2029
Wed 28 Mar 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 28 Mar 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can present each of his apps in 2 minutes: what it does, how he built it, and one hard thing he fixed. Components: (No new app — rehearsal day, using the portfolio app.) LabelTitle, Text "Showcase rehearsal", FontSize 22; LabelTimer, Text "2:00", FontSize 32, Bold true; ButtonStartTimer, Text "Start 2-minute timer"; Clock1, TimerInterval 1000; LabelTalk, Text "Talk plan: 1) What it does 2) How I built it 3) One hard bug I fixed"; ListViewApps (the portfolio list from Session 122); LabelFeedback, Text "Feedback: "; TextBoxFeedback, Hint "What was clear? What was confusing?". Step-by-step build:

1) Designer setup: A simple rehearsal timer app (or use the phone's timer): big timer label, Start button, Clock1, the talk-plan label, the portfolio app list, and a feedback TextBox. Add Clock1 (non-visible).

2) Blocks setup: a) global variable secondsLeft = 120. b) when ButtonStartTimer.Click → set secondsLeft to 120 → set LabelTimer.Text to "2:00" → call Clock1.TimerEnabled to true. c) when Clock1.Timer → set secondsLeft to secondsLeft − 1 → set LabelTimer.Text to (join (secondsLeft ÷ 60) + ":" + (if secondsLeft mod 60 < 10 then join "0" + (secondsLeft mod 60) else secondsLeft mod 60)) → if secondsLeft ≤ 0 then call Clock1.TimerEnabled to false → set LabelTimer.Text to "Time! Wrap up in one sentence.". d) Rehearsal script per app (2 minutes): 0:00–0:30 what the app does — demo it live on the phone; 0:30–1:15 how he built it — name one component and one block (e.g. "I used TinyDB1 to save the best score"); 1:15–1:50 one hard bug and how he fixed it; 1:50–2:00 one sentence: who the app is for. e) After each talk, Ray/Run/Rica write one line of feedback in TextBoxFeedback: one thing that was clear, one thing that was confusing.

3) Test: the timer counts down from 2:00 and stops at 0 with the wrap-up message; every app gets one timed run; feedback is collected for each app.

90-minute timing: 0–10 plan/sketch — write the 4-part talk plan for the lead app; 10–20 demo — Rica gives a 2-minute demo talk for one app; 20–65 build — rehearse Capstone 2 and Capstone 3 (2 minutes each, timed); 65–80 test & fix — rehearse two more portfolio apps and fix the talks (cut the longest part); 80–90 share — pick the best talk and repeat it once, cleanly. Test checklist: Each talk fits in 2 minutes (timer proves it); each talk has all four parts (what, how, bug, who for); the live demo works during the talk; feedback names one clear and one confusing thing. Common bug: the talk runs over because the demo takes too long — fix: rehearse the demo with the app already open on the right screen, and cut the "how I built it" part to one component and one block only. Success check: Gin can give a timed 2-minute talk for at least two apps, with a live demo, a build detail, and a bug story. Homework: Practise the full showcase order once at home (or in his head): Capstone 2, Capstone 3, then the best portfolio app — 2 minutes each.

Session 125Showcase 1 — present Capstone 2 + 3 to Ray, Run and RicaWed 4 Apr 2029
Wed 4 Apr 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 4 Apr 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can present Capstone 2 and Capstone 3 to a real audience (Ray, Run, and Rica), demo them live, and answer questions. Components: (No new app — showcase day, using the finished Capstone 2, Capstone 3, and portfolio apps.) LabelTitle, Text "Showcase 1 — Capstone 2 + 3", FontSize 22; LabelTimer, Text "2:00", FontSize 32, Bold true; ButtonStartTimer, Text "Start timer"; Clock1, TimerInterval 1000; LabelQuestions, Text "Questions from Ray, Run and Rica:"; ListViewQuestions; TextBoxQuestion, Hint "Ask Gin a question"; ButtonAddQuestion, Text "Add question". Step-by-step build:

1) Designer setup: The rehearsal timer from Session 124, plus a questions list: a question TextBox + Add button + ListView. Have both capstone apps open and ready on the phone before starting — no building during the showcase.

2) Blocks setup: a) Timer blocks exactly as Session 124 (120 seconds, countdown, "Time! Wrap up" at 0). b) when ButtonAddQuestion.Click → if TextBoxQuestion.Text ≠ "" then add item TextBoxQuestion.Text to list (ListViewQuestions.Elements) → set TextBoxQuestion.Text to "" — the question list is just a list, no TinyDB needed for the day. c) Showcase order: (1) Capstone 2 — 2-minute talk + live demo + questions; (2) Capstone 3 — 2-minute talk + live demo + questions; (3) Ray and Run try both apps themselves for 5 minutes each and say one thing they liked and one thing that confused them; (4) Rica notes the fixes for Session 126.

3) Test: both apps open and work before the audience arrives; the timer runs for each talk; every question gets an answer or an honest "I don't know yet — I'll check".

90-minute timing: 0–10 plan/sketch — set up the phone, open both apps, check the timer; 10–20 demo — (no demo; the showcase IS the demo) quick sound check: one tap in each app; 20–65 build — present Capstone 2 (talk + demo + questions) and Capstone 3 (talk + demo + questions); 65–80 test & fix — Ray and Run playtest both apps and give feedback; 80–90 share — Rica reads back the fix list for Session 126 and Gin picks his favourite moment. Test checklist: Both talks fit in 2 minutes; both live demos worked in front of the audience; every audience question was answered or parked honestly; the fix list for Session 126 is written down. Common bug: the demo fails live (e.g. the phone is not connected to Companion) — fix: before the showcase, open both apps on the phone and leave them running; if Companion drops, use the built .apk installed on the phone instead of rebuilding live. Success check: Gin presented both capstones live to Ray, Run, and Rica, answered questions, and has a written fix list for Session 126. Homework: Fix nothing yet — just re-read the fix list and circle the three most important items for Session 126.

Session 126Final fixes — last bugs, tidy all apps, back up project files (.aia)Wed 11 Apr 2029
Wed 11 Apr 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 11 Apr 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can fix the last bugs from Showcase 1, tidy every app, and back up all project files (.aia) so nothing is lost. Components: (All finished projects — no new app.) LabelTitle, Text "Final fixes + backup", FontSize 22; ListViewApps, Elements "Capstone 2,Capstone 3,Portfolio app,Best Phase 7 app"; ListViewFixes, Elements empty; TextBoxFix, Hint "Fix done: what, in which app?"; ButtonAddFix, Text "Log fix"; LabelBackup, Text "Backed up: 0 of 4 (.aia files)"; ButtonBackup, Text "Mark app backed up"; TinyDB1 (tag "final_fixes"). Step-by-step build:

1) Designer setup: A simple fix-log app (or paper list): title, apps ListView, fix TextBox + Log button, fixes ListView, backup label + button. Add TinyDB1.

2) Blocks setup: a) global variable fixList = create empty list; global variable backedUp = 0. b) when Screen1.Initialize → set fixList to call TinyDB1.GetValue tag "final_fixes" valueIfTagNotThere (create empty list) → set ListViewFixes.Elements to fixList. c) when ButtonAddFix.Click → if TextBoxFix.Text ≠ "" then add item (join ListViewApps.Selection + ": " + TextBoxFix.Text) to list fixList → call TinyDB1.StoreValue tag "final_fixes" valueToStore fixList → set ListViewFixes.Elements to fixList → set TextBoxFix.Text to "". d) when ButtonBackup.Click → set backedUp to backedUp + 1 → set LabelBackup.Text to (join "Backed up: " + backedUp + " of 4 (.aia files)") → if backedUp ≥ 4 then set LabelBackup.Text to "All backed up! ✅". e) The real work: work through the Session 125 fix list top to bottom; after each fix, re-test that app's known answers; then tidy: same colours, same button sizes, no placeholder text ("Label1", "Text for Button1") left anywhere, no dead buttons that do nothing. f) Backup, app by app: in App Inventor, open the project → Projects → Export selected project (.aia) to my computer → save the file with the app's name and today's date (e.g. ElectronicsLab-2029-04-11.aia); repeat for Capstone 2, Capstone 3, the portfolio app, and the best Phase 7 app; check each file exists and is not 0 KB.

3) Test: every fix on the list is logged and re-tested; all four .aia files exist with sensible sizes; no app still shows placeholder text; all three capstone/portfolio apps still open and work.

90-minute timing: 0–10 plan/sketch — read the Showcase 1 fix list, order it; 10–20 demo — Rica exports one .aia live and checks its size; 20–65 build — fix round (top bugs first, then tidy); 65–80 test & fix — re-test every fixed app, then back up all four .aia files; 80–90 share — show Ray and Run the tidy apps and the four backup files. Test checklist: Every fix is logged; every fixed app is re-tested; four .aia files exist and open (re-import one to prove it works); no placeholder text remains in any app. Common bug: the exported .aia is missing the newest fix — fix: export AFTER the last fix, not before; the .aia is a snapshot of the project at export time, so re-export any app fixed after its first export. Success check: Gin has fixed the Showcase 1 list, tidied all apps, and has four named, dated .aia backup files that re-import cleanly. Homework: Write his final showcase talk outline: what he learned, his favourite app, and what is next (one sentence each).

Session 127Final showcase — present the full portfolio, what he learned, what is nextWed 18 Apr 2029
Wed 18 Apr 2029 | Phase 8 — Capstone & Portfolio

Date: Wed 18 Apr 2029 | Phase: Phase 8 — Capstone & Portfolio Learning objective: Gin can present his full portfolio, explain what he learned across 127 sessions, and say what he wants to build next. Components: (No new app — final showcase, using the portfolio app.) LabelTitle, Text "Final showcase — Gin's portfolio", FontSize 22; LabelTimer, Text "2:00", FontSize 32, Bold true; ButtonStartTimer, Text "Start timer"; Clock1, TimerInterval 1000; LabelLearned, Text "What I learned: "; LabelNext, Text "What is next: "; ListViewApps (the polished portfolio list from Session 123). Step-by-step build:

1) Designer setup: The portfolio app from Session 123 (polished, with screenshots) plus the rehearsal timer from Session 124. Have the phone ready with the portfolio app open and the .aia backups from Session 126 to show.

2) Blocks setup: a) Timer blocks as Session 124 (120 seconds per app, "Time! Wrap up" at 0). b) Showcase order: (1) Open the portfolio app and flip through it — one minute per lead app (Capstone 2, Capstone 3, best Phase 7 app), 2-minute talk each as rehearsed; (2) What he learned — three sentences, prepared in Session 126 homework (e.g. "I learned to save data with TinyDB, to test like a user, and to fix bugs one at a time"); (3) What is next — one sentence (e.g. a new app idea, or improving one capstone); (4) Questions from Ray, Run, and Rica; (5) Show the four .aia backup files as proof the work is saved. c) No new building — if something breaks live, say so honestly, note it, and move on; the showcase is a presentation, not a fix session.

3) Test: the portfolio app opens and every screenshot loads; the timer works; the three "what I learned" sentences and the "what is next" sentence are written down before starting.

90-minute timing: 0–10 plan/sketch — set up, open the portfolio app, check screenshots and timer; 10–20 demo — (no demo; the showcase is the event) one-minute warm-up: present the lead app once; 20–65 build — present Capstone 2, Capstone 3, and the best portfolio app (2 minutes each + questions); 65–80 test & fix — "what I learned" + "what is next" + audience questions; 80–90 share — celebrate: Rica notes the full journey (127 sessions, 18 Nov 2026 – 18 Apr 2029) and Gin picks the one app he is proudest of. Test checklist: Every portfolio app presented with a live demo; the "learned" and "next" sentences were said out loud; questions were answered or parked honestly; the .aia backups were shown. Common bug: running out of time before the last app — fix: keep the 2-minute timer visible and cut the middle of a talk, never the demo; the demo is what the audience remembers. Success check: Gin presented his full portfolio live, explained what he learned and what is next, and finished the 127-session journey with working apps and backups. Homework: Keep building: pick one idea from "what is next" and build the first screen of it in the next free session — the journey continues past Session 127.

← Back to all lesson plans