A pocket device for real-world quests

What you will work towards

A small touchscreen that suggests activities and records progress away from your phone.

CAIBI’s proposed addition: Choose the licensed GoQuest build or develop an original offline task picker with your own content, saved progress and a measured case.

Guide version 1.0. AI can help explain, adapt and debug; you still measure, assemble and test the physical result.

Start with the original

Paid creator build

• Paid creator build · view source material ↗

Source inspected 10 October 2026. Creator supplies printable files and licensed firmware access for a Waveshare ESP32-S3 1.75-inch AMOLED. This is not an open-source firmware base. Not built or assessed by CAIBI.

From source to something you can finish

What the source provides: GoQuest provides a licensed creator route for a portable activity device.

What still needs doing: The CAIBI route is original software and task content; it does not unlock or modify proprietary firmware.

Your first milestone: Show one of your own activities on a working USB-powered display.

Parts to confirm before buying

• An ESP32 display board with a working manufacturer touch example; record its exact revision
• USB data cable and a suitable USB supply for the first prototype
• Measured board dimensions, connector positions and access to reset before designing a case

Use the source wiring and bill of materials as the starting point. Confirm exact variants, availability, tools and complete cost before ordering.

The completion route

1. Write ten original activities and sketch three screens: choose, current activity and completed. Decide whether progress resets manually or by date; omit dates until a trustworthy clock is available.
2. Run the board manufacturer display and touch examples unchanged. Record the working library versions and orientation.
3. Implement the task picker with local data. Add complete, skip and reset controls, and save only when progress changes.
4. Restart the device and check saved progress. Add an explicit reset confirmation and a recoverable empty-data state.
5. Print a connector and mounting fit coupon, then a USB desk case. Treat portable power as a later board-specific design.

Prompts to move it forward

Copy a prompt into your AI tool with the source material and your actual parts. Work through one small step at a time and check the output before using it. Choose an AI tool or practise the skills first.

Review the source material I supply for A pocket device for real-world quests. Make a table of what is provided, missing, contradictory or dependent on a paid service. Identify exact hardware revisions, firmware files, library versions, CAD files and licences. Separate creator claims from your proposed additions. Do not fill gaps with guessed specifications. Finish with one small test that can resolve the biggest uncertainty before I buy parts.

Sources:
Paid creator build: https://creative-chance.com/products/goquest

Help me build an original offline activity picker, inspired by the idea of a dedicated quest device. Do not copy GoQuest firmware, artwork or task content. Ask for my exact display board, working vendor example, library versions and ten activities I wrote. First propose a small state model and plain-text screen layout. Then implement one screen at a time using the working example. Store progress only when it changes; include empty-list handling, restart recovery and a confirmed reset. Do not add accounts, network access or a date-based streak without a reliable time source. Give me manual tests and clearly separate proposed code from tested behaviour.

Sources:
Paid creator build: https://creative-chance.com/products/goquest

Design a removable USB desk enclosure for my activity picker. Request measured board dimensions, mounting holes, touch area, reset access and the actual cable plug. Start with a mounting and connector fit coupon. Keep the touch surface unobstructed. Do not include a battery compartment until I supply the board charging documentation and an independently checked power design.

Sources:
Paid creator build: https://creative-chance.com/products/goquest

Create a test log for A pocket device for real-world quests. Intended outcome: A small touchscreen that suggests activities and records progress away from your phone. Separate expected behaviour from observed results. Include power restart, disconnected inputs, communication failure and the actual physical use. Ask me to provide results, firmware versions, changes, photos and unresolved problems. Never mark a test passed without my evidence.

Sources:
Paid creator build: https://creative-chance.com/products/goquest

What to test and record

• All original activities can be selected and long text stays readable.
• Complete and skip do not accidentally double-count a touch.
• Restart preserves committed progress; corrupt or missing saved data gives a usable default.
• Reset requires confirmation, and cancelling it preserves progress.
• USB plug, touch area and reset remain accessible after case assembly.

Keep photos, exact parts and software versions with the test log. Failed or incomplete attempts are useful evidence too.

A possible next version

After the desk prototype works, explore a portable version using documented compatible power hardware. The licensed GoQuest route remains available separately for people who want the creator package.