{
  "edition": {
    "edition": "2026-09-06-draft-01",
    "language": "en",
    "publicationState": "published",
    "sourceRevision": "a7e788eb4b151fd92c1f58153e015773e3a829af",
    "projectCount": 67,
    "documentCount": 94,
    "skillCount": 10,
    "archivePath": "library.zip",
    "archiveBytes": 181812,
    "releasedAt": "2026-09-08T05:03:11.129+00:00"
  },
  "access": {
    "released": true,
    "rehearsal": false
  },
  "project": "native-phone/treasure-hunt.md",
  "markdown": "https://legion.tw/api/projects/packet.md/native-phone/treasure-hunt.md?edition=2026-09-06-draft-01",
  "documents": [
    {
      "path": "native-phone/README.md",
      "text": "# Native phone applications\n\n[All project types](../README.md) · [Shared launch](../shared/launch.md)\n\nBuild around life away from the desk. Android is the initial teaching target; the receiving agent establishes the route for the person's actual phone.\n\n## Projects to build\n\n- [Capture photographs for a report on site](photo-report-companion.md)\n- [Workout companion](workout-companion.md)\n- [Capture a spoken thought](voice-capture.md)\n- [Home measurements and replacement parts](home-measurements.md)\n- [Treasure hunt](treasure-hunt.md)\n- [Practice notebook with recordings](practice-notebook.md)\n- [Field notebook for an interest](field-notebook.md)\n- [Personal todo app](personal-todo.md)\n- [Notes that reach the agent's workspace](agent-readable-notes.md)\n- [Chat with your coding agent from your phone](coding-agent-in-your-pocket.md)\n\nThese are instructions for projects you can build with your coding agent.\n"
    },
    {
      "path": "native-phone/treasure-hunt.md",
      "text": "# Build a treasure hunt for your friends\n\nBuild 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).\n\nDevelop 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.\n\n## Give the organizer a way to create\n\nLet 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.\n\nChoose 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.\n\nKeep 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.\n\n## Make it good while people are out\n\nShow 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.\n\nGive 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.\n\nBuild 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.\n\nShape 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.\n\n## Let the adventure finish\n\nGive 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.\n\nPreserve 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.\n\nMake 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.\n\n## Play the hunt\n\nDeliver 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.\n\nExplain 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.\n"
    }
  ]
}