An operations dashboard for your actual work.

Build the smallest useful version

Copy the prompt into Apps and use the fictional records for the first version. Explain what the user needs to decide from the screen. Ask for a preview and requirement checks before adding more features.

This starter is a brief and dataset, not a deployed application or a one-click import. Paste it into Workspace yourself. Adding a real spreadsheet later does not imply that future spreadsheet changes synchronize automatically.

Test the numbers and the interactions

Check the three expected counts, apply the Maya filter, and clear it. Try an empty result and a record with missing data. If the App allows edits, reload it and verify the behavior promised by the build.

Review the preview on desktop and phone-sized screens. Ask for fixes to labels, keyboard access, or incorrect filters in the App conversation. Use saved build history to choose the version you want, then decide whether private sharing or public publication fits the data.

Try it with a small example.

An illustrative result.

Fictional sample, written to show the expected structure. Your result depends on your inputs and needs review.

Fictional sample checks
All records: 3
Open: 1 · In progress: 1 · Done: 1
Owner Maya: 2 records
Unknown due dates: 3
No overdue count should be invented from missing dates.

Before you use the result.

• Initial counts match the three sample rows.
• Owner filters can be applied and cleared.
• Unknown due dates stay unknown.
• Edit persistence matches the stated behavior after reload.
• The result is private until you choose otherwise.