FOUR EDUCATIONAL PROJECTS
AppStruct examples you can work through.
Build a no-code request app, inspect a spreadsheet tracker, draft a project brief or prepare a status presentation. These outlines use fictional data and define checks you can repeat in your own practice resources.
Each example uses an independent app, workbook, document or presentation. The Sheets tracker is separate from the App Builder database; the Docs and Slides examples have their own source notes. Follow one complete guide and record your observed result.
APP BUILDER EXERCISE
Build a service request app
Let a person submit a request, then let the team find the saved record and update its status.
Fictional input
Create a separate practice app using the guide’s field mapping. Save two fictional requests. Read the saved records and record their actual identifiers.
- customer_name
- Alex Example
- contact_email
- [email protected]
- service
- Consultation
- details
- Describe an example request
- status
- New, In progress or Resolved
Work through the task
- Plan a request form, a team list and a detail screen. Define who may submit, read and update a request.
- Connect the form inputs to a save action and map the saved records to the list.
- Open one request by its identifier and configure the selected-record status update.
- Repeat the workflow in the published app, including an invalid form and a failed save.
Check before calling it finished
A valid request is still present after reopening the app. Updating the selected request changes only its status; the other request remains unchanged. A failed save is not shown as a success.
SHEETS MCP EXERCISE
Track requests in a spreadsheet
Use an assistant to inspect a practice tracker, add a request and update one existing row.
Fictional input
In a separate workbook named Service requests — practice, create a Requests sheet and enter the guide’s A1:E3 table.
- Request IDs
- DEMO-001 and DEMO-002
- Customer
- Example A and Example B
- Service
- Consultation or Maintenance
- Status
- New or In progress
- Notes
- Fictional installation or example device
Work through the task
- Save the workbook and connect Sheets MCP with the permissions needed for the exercise.
- Discover the workbook and sheet identifiers, then read the bounded request range.
- Review and append DEMO-003 from the guide, then read the saved row back.
- Locate DEMO-001 by its request ID and change only its Status cell to Resolved.
Check before calling it finished
DEMO-001 reads Resolved; its other fields are unchanged. DEMO-002 remains In progress and the appended DEMO-003 remains New. Read the range back and inspect the saved workbook in its editor.
DOCS MCP EXERCISE
Turn meeting notes into a project brief
Prepare a reviewable brief from a small meeting record while preserving the original notes.
Fictional input
Use the published fictional meeting-notes text for DEMO-BRIEF-001 in a separate practice document.
- Goal
- Test a service-request pilot
- Scope
- A request form, team list and detail view
- Actions
- DEMO-A1 and DEMO-A2, with named example owners
- Unknowns
- Budget, data store and launch date not agreed
- Review state
- Draft for review
Work through the task
- Open a practice document, paste the source notes and connect Docs MCP.
- Find the document, read the notes and review a proposed brief against the source.
- Create a separately saved brief, keeping unknown decisions visible.
- Read the saved brief back, then follow the guide’s optional exact-text correction.
Check before calling it finished
The separate brief matches the agreed scope and keeps unresolved decisions unresolved. The original notes remain intact, and the reviewed correction is present in the saved brief.
SLIDES MCP EXERCISE
Prepare a project status presentation
Turn source notes into five slides, then update one Progress slide using a later fictional snapshot.
Fictional input
Use the DEMO-STATUS-001 practice notes. Snapshot A is the initial source; Snapshot B supplies one later update.
- Slide outline
- Goal, Progress, Risks, Next steps, Decisions needed
- Check IDs
- DEMO-CHECK-01, DEMO-CHECK-02 and DEMO-CHECK-03
- Speaker notes
- Source context and checks still open
- Unknowns
- Budget, data store and launch date not agreed
- Later change
- Only the reviewed Progress-slide body
Work through the task
- Review Snapshot A, connect Slides MCP and create the five-slide practice deck.
- Inspect actual slide identifiers, titles, body slots and speaker notes.
- Use Snapshot B to prepare the complete final body for the selected Progress slide.
- Read the saved deck back and reopen it in the presentation editor for a visual check.
Check before calling it finished
Only the intended Progress body changes. Its title and notes, the other four slides, their order and the unresolved decisions stay intact. Fictional check states remain teaching inputs.
Choose the next check for your project.
Use the guides and worksheets directory to continue with data, costs or another Workspace task. For a published app, the cross-platform release guide helps you repeat the same workflow on each intended destination. Check each target separately.