A shopping list is a useful first Power Apps exercise because the data is simple and mistakes are reversible. Build it with a Microsoft List or SharePoint list, generate a responsive canvas app, then test creation, editing, deletion and permissions before adding automation.
Use an approved Microsoft 365 environment. Do not create a developer tenant or buy a separate licence merely because an old tutorial tells you to.
1. Create the list
Create a list called Shopping Items with these columns:
| Column | Type | Purpose |
|---|---|---|
| Title | Single line of text | Item name |
| Quantity | Number | Amount required |
| Category | Choice | Produce, household, other |
| Purchased | Yes/No | Completion state |
| Notes | Multiple lines of text | Optional detail |
Add a few disposable records. Avoid personal or sensitive information because this is a practice build.
2. Generate the canvas app
Microsoft's current route from Power Apps is:
- Sign in to Power Apps.
- Select Start with data.
- Select SharePoint.
- Connect to the site.
- Select the list and choose Create app.
You can also open the list and select Integrate > Power Apps > Create an app.
Newly generated apps use a single responsive screen. Older tutorials often show separate browse, detail and edit screens. Those older apps can continue to work, but a new build may not resemble the screenshots.
3. Inspect before customising
Preview the generated app. Add an item, edit it and delete a test record. Confirm that each change appears in the list.
Inspect the controls and formulas Power Apps generated. Do not replace a working form with a handwritten Patch formula until you understand validation, errors and data types. Generated apps provide a safer starting point for a beginner.
4. Make two useful changes
First, filter out purchased items from the main view, or provide an obvious toggle to include them. Second, sort remaining items by category and name.
When you edit a formula, test blanks, unusual quantities and apostrophes in item names. Power Fx uses your authoring locale, so separators shown in another person's tutorial may differ.
5. Save, publish and share deliberately
Save and publish the app. Share it only with intended users. Sharing the app does not automatically grant access to the underlying list, so grant the least list permission needed and test with a non-owner account.
If this is a family exercise in a work tenant, check policy before sharing with external or guest users. Consumer Microsoft accounts and organisational Entra accounts have different boundaries.
6. Add automation only when the app works
A Power Automate notification is optional. If you add one, make it low risk, such as a reminder when a new item is created. Protect against duplicate runs and avoid sending messages to addresses typed by untrusted users.
Power BI is not necessary for a tiny shopping list. Add reporting only when there is a real analytical question. More products do not make a better practice project.
Test checklist
- create, edit and delete a disposable item
- test blank and invalid values
- test phone and desktop widths
- test as a shared non-owner
- confirm list permissions
- document the owner and removal route
Sources
- Create a canvas app with data from a list
- Connect to SharePoint from a canvas app
- Save and publish a canvas app
- Share a canvas app
Get help with the next build decision
The Power Apps Builders Space is for people turning small practice apps into maintainable work. Share a sanitised description, not tenant URLs or family details.