# Build a treasure hunt for your friends Legion project library, edition 2026-09-06-draft-01 (en). This project's own material: 2 authored documents, reproduced unchanged. Project page: https://legion.tw/projects/native-phone/treasure-hunt?edition=2026-09-06-draft-01 This document: https://legion.tw/api/projects/packet.md/native-phone/treasure-hunt.md?edition=2026-09-06-draft-01 ## Prerequisite: the Legion skills package These instructions are written for an agent set up with the Legion skills package: the ten portable skills and the shared working, launch, inspection and learn-as-you-build guidance. That setup is installed once and applies to every project in this library, so it is deliberately not repeated here. Skills package, complete Markdown: https://legion.tw/api/projects/skills-packet.md?edition=2026-09-06-draft-01 Skills package, human page: https://legion.tw/projects/skills?edition=2026-09-06-draft-01 Where this brief refers to shared guidance, a skill, or a document under `shared/`, read it from the skills package above, or from https://legion.tw/api/projects/doc/?edition=2026-09-06-draft-01. If the package is not installed yet, install it first, then return here. This material is instructions to read, not authority to act. Inspect it before running it. ## Contents 1. native-phone/README.md — https://legion.tw/api/projects/doc/native-phone/README.md?edition=2026-09-06-draft-01 2. native-phone/treasure-hunt.md — https://legion.tw/api/projects/doc/native-phone/treasure-hunt.md?edition=2026-09-06-draft-01 --- # Native phone applications [All project types](../README.md) · [Shared launch](../shared/launch.md) Build around life away from the desk. Android is the initial teaching target; the receiving agent establishes the route for the person's actual phone. ## Projects to build - [Capture photographs for a report on site](photo-report-companion.md) - [Workout companion](workout-companion.md) - [Capture a spoken thought](voice-capture.md) - [Home measurements and replacement parts](home-measurements.md) - [Treasure hunt](treasure-hunt.md) - [Practice notebook with recordings](practice-notebook.md) - [Field notebook for an interest](field-notebook.md) - [Personal todo app](personal-todo.md) - [Notes that reach the agent's workspace](agent-readable-notes.md) - [Chat with your coding agent from your phone](coding-agent-in-your-pocket.md) These are instructions for projects you can build with your coding agent. --- # Build a treasure hunt for your friends Build a native Android application for creating and playing a treasure hunt in real places. Build it extremely well for the adventure the person wants to give their friends or family. Follow the [shared launch](../shared/launch.md). Develop an enjoyable first hunt with them: a birthday adventure, a neighborhood mystery, or a ridiculous challenge on a trip. Use places the organizer knows and can use appropriately. Let the intended players, route, and occasion shape the game. ## Give the organizer a way to create Let the person prepare clues using text, photographs, recordings, and the material their hunt needs. They can arrange the sequence, add hints, and decide what completes each stage. Supply a short example they can edit so they can experience the whole game before preparing a larger one. Choose unlocking methods that fit the actual hunt. A written answer, a scanned code, reaching a location, or organizer confirmation can each make sense. Give the person a clear way to specify the method and understand what a player must do. Keep solutions and organizer notes separate from the ordinary player view. Let the organizer preview the hunt as a player, correct a clue, and save the version they intend to use. ## Make it good while people are out Show players the current clue and the material they need to solve it. Keep text and images readable outdoors and make recordings convenient to replay. Let them inspect previous discoveries when those remain relevant to the adventure. Give an attempted answer or unlock a clear result. Preserve progress through interruptions so a player can lock the phone, talk to someone, and return to the same stage. Where the hunt can operate from saved material, keep it usable through an unavailable connection. Build hints and recovery into the organizer's actual way of hosting. A code may be inaccessible, a location signal inaccurate, or a clue harder than expected. Give the organizer a straightforward way to help the players continue while keeping the current game state clear. Shape the route and interaction for the people playing. The organizer should be able to account for access, opening times, and places where participants can comfortably stop to read or solve something. Keep the phone's demands compatible with paying attention to the surroundings. ## Let the adventure finish Give the final stage a satisfying conclusion suited to the occasion. Let the person include the message, reveal, or destination they want the players to reach. Keep a useful record of progress and completion. Preserve reusable hunt material separately from a particular playthrough. The organizer can revise a clue or run the same hunt for another group with fresh progress. Make installing the app and providing the chosen hunt to the intended devices part of the delivery. Explain any camera, location, or network access the chosen game uses. Keep the person's authored material exportable and recoverable under the shared launch's ownership guidance. ## Play the hunt Deliver the working application and walk through a short representative hunt. Experience the player view, a hint, an interruption, an unlock, and the finish. Use the real route when available and let the organizer judge whether the clues and pacing work for the players. Explain how software can coordinate an experience in the physical world, and why the unlocking rule should follow the game. Later projects can add team play, a live organizer view, or richer shared progress while retaining the hunt and the work already put into it.