TreasureLink Mini
TreasureLink Mini is a treasure-hunt app I'm developing with Flutter. The idea is to make treasure hunts more interactive and enjoyable by combining hand-drawn maps, checkpoints, riddles, QR codes, and location-based features in one app.
The app has two main modes. In Organizer Mode, the organizer can set up an expedition and draw a map using their finger. In Player Mode, players can view that map, explore checkpoints, solve clues, and track their progress throughout the adventure.
I want the app to feel like a real treasure-hunting experience, not just another ordinary mobile app. My goal is to create something that feels mysterious, exciting, and immersive while keeping it simple enough for anyone to use.
Supplies
Tools and Technologies Used
TreasureLink Mini is being developed using Flutter, which allows me to build the app for Android using a single codebase. The main programming language is Dart.
The project uses several Flutter packages to support its features:
- Flutter and Dart: Used to build the app's interface, functionality, and overall structure.
- Geolocator: Used for GPS and location-related features.
- Mobile Scanner: Used to scan QR codes through the phone's camera.
- Shared Preferences: Used to save information locally, such as completed checkpoint progress and the organizer's map.
The app is developed on a Windows computer, with testing carried out on a Android 11.
These tools provide the foundation for the app's main features, including map drawing, checkpoint exploration, QR scanning, and progress tracking. I also plan to improve the visual experience with suitable fonts, illustrations, icons, and animations while keeping the app smooth and usable on the target device.
Overview of TreasureLink Mini
TreasureLink Mini brings the main parts of a treasure hunt together in one place. Instead of relying entirely on paper maps and written clues, the app lets organizers create an expedition and gives players a simple way to follow the adventure.
The app has two main modes. Organizer Mode is used to set up an expedition and draw a custom map. Player Mode allows players to view that map, explore checkpoints, solve riddles, scan QR codes, and keep track of their progress.
The app also includes GPS and location features to support the exploration experience. Map drawings and player progress are saved locally so that important information can remain available when the app is reopened.
The main goal is to make organizing and participating in a treasure hunt easier while keeping the experience fun, interactive, and engaging. I want TreasureLink Mini to combine the simplicity of a mobile app with the excitement of discovering something hidden.
The Story Behind the App
The adventure begins with the organizer, who prepares an expedition and draws a custom map using their finger. The map can represent a route, important landmarks, or places players need to explore. Once the map is saved, players can open the expedition and use it as their guide.
As players progress, they can visit checkpoints, solve riddles, and scan QR codes to interact with different parts The idea behind TreasureLink Mini is to bring the excitement of a real treasure hunt into a mobile app. I wanted to create something where people could do more than just look at a map or read clues. The app should let themof the hunt. Their progress is tracked along the way, giving them a clear sense of how far they have come.
I want the experience to feel mysterious and engaging, as if every checkpoint brings players one step closer to uncovering something hidden. At the same time, the app should remain practical and easy to use, making it possible for people to organize their own treasure hunts without needing complicated equipment or software.
Ultimately, TreasureLink Mini is about turning an ordinary treasure hunt into a more interactive experience that brings together exploration, puzzles, creativity, and technology.
How the App Works
TreasureLink Mini is designed to make a treasure hunt easy to set up and fun to experience. The process starts with the organizer preparing an expedition and ends when players complete the adventure.
First, the organizer opens the app and enters the expedition details, including the organizer's name and the expedition name. They can then draw a custom map directly on the screen using their finger. Once the map is ready, it can be saved and viewed in Player Mode.
Players can then open the player interface and view the organizer's map. They can explore the available checkpoints, follow clues, solve riddles, and scan QR codes as part of the hunt. The app also includes GPS and location features to support the exploration experience.
As players complete checkpoints, their progress is saved so they can see how much of the adventure they have completed. The saved map and player progress are stored separately, allowing the map to remain available even if the player's progress is reset.
The overall process is simple: prepare the expedition, draw the map, explore the checkpoints, solve the clues, and complete the treasure hunt.
Organizer Mode
Organizer Mode is where the treasure hunt is prepared. It allows the organizer to set up an expedition, draw a custom map, and save it for players to use during the adventure.
When the app opens, the organizer can enter their name and the expedition name. They can then draw directly on the screen using their finger, creating a map that suits the location and type of treasure hunt.
4.1 Setting Up an Expedition
Flutter's TextField widget can collect the organizer's name and expedition name.
These controllers hold the text entered by the organizer. The app can use the values when creating the expedition.
4.2 Drawing the Treasure Map
The main feature of Organizer Mode is the ability to draw a map freely using a finger. The organizer can sketch paths, landmarks, and other visual clues.
Flutter's GestureDetector captures finger movements, while CustomPaint displays the drawing.
The gesture callbacks track the finger's movements. A custom painter then uses the recorded points to draw the strokes on the canvas.
4.3 Editing the Map
The organizer should be able to undo the last stroke or clear the map before saving it.
For example, an undo function can remove the most recent stroke:
Here, strokes represents the collection of drawing strokes. Calling setState() refreshes the interface after the last stroke is removed.
A clear-map function can remove all strokes, preferably after asking the organizer for confirmation.
4.4 Saving the Map
Once the drawing is ready, the organizer needs to save it so that it can be displayed in Player Mode.
The app uses SharedPreferences for local storage. A simplified example is:
Here, mapData represents the drawing converted into a format that can be stored as JSON. The actual implementation must convert the stroke coordinates into serializable data before saving.
Using normalized coordinates helps preserve the drawing's proportions when it is displayed on screens of different sizes.
4.5 Starting the Expedition
After saving the map, the organizer can proceed to Player Mode. The player screen should load the saved drawing and display the same map created by the organizer.
The map should remain available after the app is closed and reopened. Its stored data should also be kept separate from player progress, so resetting completed checkpoints does not delete the map.
Organizer Mode provides the tools needed to prepare a custom treasure hunt, making it easy for organizers to create, edit, and save a map before players begin their adventure.
Setting Up an Expedition
Setting up an expedition is the first step in creating a treasure hunt. In Organizer Mode, the organizer enters the basic details of the adventure before moving on to draw the map.
The organizer can enter their name and choose a name for the expedition. These details help identify the treasure hunt and can be used to personalize the experience in Player Mode.
5.1 Entering Expedition Details
Flutter's TextEditingController is used to read the text entered into the input fields.
The organizer's name and expedition name can be collected using TextField widgets:
The controllers make it possible for the application to access the entered values when the organizer proceeds to the next screen.
5.2 Starting the Expedition
Once the details have been entered, the app can use a button to move to the next screen.
This is a simplified example of navigation to a map-drawing screen. The screen name should match the actual class used in the project.
The setup process should be straightforward, allowing the organizer to move naturally from entering the expedition details to creating the treasure map.
Drawing and Editing the Treasure Map
The treasure map is one of the main features of TreasureLink Mini. It allows the organizer to create a custom map by drawing directly on the screen with a finger. The organizer can sketch paths, mark important areas, and add visual details to help players understand the expedition.
6.1 Drawing on the Canvas
Flutter's GestureDetector can capture finger movements, while CustomPaint displays the drawing on the screen.
The gesture callbacks track the finger's movement, and a custom painter uses the recorded points to render the map. This allows the organizer to draw freely instead of selecting from a fixed set of map templates.
6.2 Editing the Drawing
While drawing the map, the organizer may need to correct mistakes or make changes. An undo feature can remove the most recent stroke.
Here, strokes represents the collection of recorded drawing strokes. The setState() method refreshes the interface after a stroke is removed.
A clear-map option can remove the entire drawing, preferably after asking the organizer to confirm the action.
6.3 Saving the Map
After completing the drawing, the organizer needs to save it so that it can be displayed in Player Mode.
The app uses SharedPreferences for local data storage. A simplified example of saving the map is:
In this example, mapData represents the drawing converted into a format that can be stored as JSON. The recorded strokes and their coordinates must be serialized before saving.
Using normalized coordinates can help the map maintain its proportions when displayed on different screen sizes.
6.4 Displaying the Saved Map
Player Mode should load the saved drawing and display the same map created by the organizer. This connects the organizer's preparation process with the player's exploration experience.
The drawing should remain available when the app is reopened, and resetting player progress should not delete it.
Overall, the drawing and editing features give organizers the freedom to create their own treasure maps while keeping the process simple and convenient.
Saving and Sharing the Map With Players
Once the organizer has finished drawing the treasure map, it needs to be saved so players can view the same map when they start the expedition. The map should remain available even after closing and reopening the app.
7.1 Saving the Map
TreasureLink Mini uses SharedPreferences to store the map data locally on the device. The map is saved separately from the players’ progress, so updating the map does not accidentally reset completed checkpoints or riddles.
For example, the app can save the map data using a dedicated key:
Here, mapData represents the information needed to recreate the organizer’s drawing. The exact structure depends on how the map is implemented in the existing code.
7.2 Loading the Saved Map
When the app needs to display the map again, it retrieves the saved data and reconstructs the drawing. This allows the organizer to prepare the map in advance instead of drawing it every time the app is opened.
The restored map should preserve the organizer’s original strokes, checkpoint placements, and other map details that are supported by the app.
7.3 Displaying the Map in Player Mode
When players open Player Mode, they should see the saved treasure map created by the organizer. The map should be displayed clearly, with the original hand-drawn paths and relevant checkpoint information remaining visible.
The player view should use the saved map rather than creating a new, empty drawing. This is important because the map is the main visual guide for the expedition.
7.4 Sharing the Map with Players
The goal is to let players access the organizer’s map easily during an expedition. If the organizer and players use the same device, the app can load the map directly from local storage.
However, SharedPreferences stores data locally on one device. It does not automatically transfer the map to another phone. If players use separate devices, an additional sharing method would be required, such as exporting the map data to a file, generating a QR code containing suitable map data, or using an online storage service.
Any sharing feature should preserve the map accurately and be simple enough to use during an outdoor treasure hunt.
7.5 Keeping the Map and Progress Separate
The saved map and player progress should be stored independently. This allows the organizer to update the treasure map without unintentionally erasing completed checkpoints or riddles.
For example, the map may use the key organizer_map_v1, while completed checkpoint progress uses completed. Keeping these values separate makes the app easier to maintain and reduces the risk of losing player progress when the map is changed.
Player Mode
Player Mode is where the actual treasure hunt takes place. It allows players to follow the organizer’s hand-drawn map, explore the area, find checkpoints, scan QR codes, solve riddles, and track their progress throughout the expedition.
The main goal is to make the experience feel like a mysterious adventure rather than a normal mobile app. The interface should be easy to understand, but it should also create a sense of exploration and discovery.
8.1 Viewing the Treasure Map
When players enter Player Mode, the app should display the map created by the organizer. The original hand-drawn paths must remain visible so players can understand the intended route and recognize important locations.
The map should fit the available screen space without unnecessarily cropping or distorting the drawing. Any checkpoint markers or other map elements should remain clearly visible.
8.2 GPS and Location Tracking
The app uses the geolocator package to access the device’s location. GPS can help players understand where they are while exploring the area.
However, GPS accuracy depends on the phone, satellite reception, and surrounding environment. The interface should communicate location information clearly without suggesting that the player’s position is always perfectly accurate.
Location permissions should also be handled properly, including cases where permission is denied or the location service is unavailable.
8.3 Finding and Completing Checkpoints
Checkpoints give the expedition structure and encourage players to explore the map. Players should be able to identify the relevant checkpoints and understand which ones they have already completed.
The interface should make the difference between completed and incomplete checkpoints easy to recognize. Any visual indicators should match the overall adventure theme without making the map difficult to read.
8.4 Scanning QR Codes
TreasureLink Mini uses the mobile_scanner package to support QR-code scanning. This can be used as part of the checkpoint experience, allowing players to scan a code associated with a particular stage of the expedition.
The scanning screen should provide clear instructions and an obvious scanning area. It should also handle camera permissions, invalid QR codes, and scanning errors gracefully.
For example, the scanner can be opened through a function like this:
This is an illustrative placeholder, not a complete implementation. The existing scanner navigation and checkpoint logic should be retained.
8.5 Solving Riddles
Riddles add a problem-solving element to the treasure hunt. Players should be able to read each clue comfortably, think about the answer, and submit it through a clear interface.
Feedback should explain whether the answer is correct or whether the player should try again. Correct answers should connect to the existing checkpoint-completion system so the expedition can progress naturally.
The visual design can use mysterious clue cards, subtle animations, and readable typography to make each riddle feel like part of the adventure.
8.6 Tracking Player Progress
The app stores completed checkpoint progress using SharedPreferences, with the existing key completed. This allows progress to remain available when the app is closed and reopened on the same device.
The Player Mode interface should display progress in a simple, understandable way. For example, completed checkpoints could receive a distinct visual marker, while remaining checkpoints retain their normal appearance.
The progress system should remain separate from the saved treasure map so that changing the map does not accidentally erase completed tasks.
8.7 Improving the Player Experience
The updated design should make Player Mode feel immersive without sacrificing usability. The map, GPS information, QR scanner, riddles, and checkpoint progress should work together as parts of one adventure.
The interface should also be optimized for the Samsung Galaxy A20s and other similar Android devices. Animations should remain smooth, text should be readable, and important controls should be easy to tap outdoors.
Most importantly, visual improvements must not break the existing functionality. The original map drawing, saved map data, location tracking, QR scanning, riddles, and progress tracking should continue to work as intended.
Viewing and Exploring the Map
The treasure map is one of the most important parts of TreasureLink Mini. It gives players a visual guide for their expedition and helps them understand the layout of the adventure. Unlike a conventional navigation app, the map is drawn by the organizer, making every expedition personal and unique.
The main objective is to let players explore the map comfortably while keeping the original drawing clear and recognizable.
9.1 Displaying the Organizer’s Drawing
Player Mode should display the map created in Organizer Mode, including the organizer’s original hand-drawn paths and other supported map elements.
The drawing should not be replaced with a generic map image. Preserving the original strokes is essential because players rely on the organizer’s drawing to understand the expedition.
The map should also fit the available screen space while maintaining its proportions as much as possible.
9.2 Zooming and Moving Around the Map
If the map is larger than the visible area, players should be able to zoom in to examine details and zoom out to see the overall layout. Panning should allow them to move around the map without accidentally activating unrelated controls.
These interactions should feel natural on a touchscreen. Zooming and panning must not distort the drawing or make checkpoint markers difficult to identify.
If these features are not already implemented, they should be added carefully without interfering with the existing map-rendering logic.
9.3 Exploring Paths and Checkpoints
Players should be able to follow the paths drawn by the organizer and identify the important locations along the way. Checkpoint markers, labels, and progress indicators should be easy to distinguish from the background and hand-drawn lines.
The design should make the map interesting to explore while avoiding excessive decoration. Visual effects should never hide the original drawing or make the intended route confusing.
9.4 Connecting the Map with GPS
GPS can provide additional context by showing the player’s current location while they explore the physical area. However, the hand-drawn treasure map is not necessarily geographically accurate or aligned with real-world coordinates.
Therefore, the app should not automatically place the GPS position directly onto the drawing unless a reliable mapping or calibration method has been implemented. The interface should clearly distinguish between the organizer’s illustrated map and the phone’s real-world location information.
9.5 Visual Design and Performance
The map-viewing experience should match the mysterious adventure theme of TreasureLink Mini. A dark background, subtle gold highlights, teal accents, and carefully designed checkpoint markers can create a consistent visual style.
Animations should be subtle and purposeful. For example, a completed checkpoint could receive a brief highlight, while map transitions could use a smooth animation.
Because the app is intended to run on devices such as the Samsung Galaxy, map rendering and interactions should remain responsive. Avoid unnecessarily complex effects that could cause lag or make the map difficult to use.
Important: Any visual redesign must preserve the organizer’s actual drawing and the existing map-saving and loading behavior. Zooming, panning, checkpoint indicators, and GPS overlays should only be introduced or modified in ways that are compatible with the current implementation.
Checkpoints and Clues
Checkpoints and clues are what turn TreasureLink Mini into an interactive treasure-hunting adventure. Instead of simply following a map, players must explore, discover locations, scan QR codes, and solve riddles to make progress through the expedition.
The aim is to make each checkpoint feel like a new stage of the adventure while keeping the system simple and reliable.
10.1 Checkpoints
Checkpoints represent important stages or locations in the treasure hunt. They give players clear goals and help organize the expedition into manageable steps.
The interface should make it easy to distinguish between checkpoints that have been completed and those that are still waiting to be discovered. Visual indicators such as highlighted markers, subtle animations, or small status icons can help players understand their progress.
Any checkpoint-related improvements must work with the existing checkpoint logic rather than introducing a separate system that conflicts with it.
10.2 Clues and Riddles
Clues guide players toward the next stage of the expedition. Some clues may require players to think carefully, interpret a message, or solve a riddle before continuing.
Riddles should be presented in a readable and engaging format. A dedicated clue card could include the riddle, an answer field, and a button to submit the answer. The design should fit the mysterious adventure theme without making the text difficult to read.
When a player submits an answer, the app should provide clear feedback. Incorrect answers should allow the player to try again, while correct answers should trigger the appropriate progression in the existing game logic.
10.3 QR-Code Checkpoints
QR codes can be used to connect physical locations with digital parts of the treasure hunt. When a player reaches a checkpoint, they can use the app's existing QR scanner to scan the relevant code.
The app should handle the scanning process smoothly and clearly communicate whether a code is recognized or invalid. Scanning a valid code should lead to the appropriate clue or checkpoint action, according to the existing implementation.
The scanner should also handle camera permissions and unexpected scanning errors without crashing the app.
10.4 Completing a Checkpoint
Once a player satisfies a checkpoint's requirements, the app should update its progress state and provide immediate feedback. For example, the checkpoint marker could change appearance, or a short animation could indicate that the stage has been completed.
Completion should be recorded using the app's existing progress-storage mechanism, including the completed key in SharedPreferences where applicable. This helps preserve progress if the app is closed and reopened on the same device.
The system should also prevent accidental duplicate completion where appropriate, without blocking legitimate retries or other intended game behavior.
10.5 Progression Through the Adventure
Checkpoints and clues should work together to create a logical sequence of discovery. Completing one stage may reveal a new clue or allow the player to continue, depending on how the organizer has configured the expedition.
The interface should clearly communicate what the player has completed and what they can do next. Avoid unnecessary pop-ups or complicated navigation that interrupt the experience.
10.6 Visual Improvements
The visual design should make checkpoints and clues feel like parts of a mysterious expedition. Gold highlights, teal accents, dark clue panels, subtle transitions, and carefully designed icons can reinforce the theme.
Animations should be short and purposeful, especially when a player solves a riddle or completes a checkpoint. The app should remain responsive on the Samsung Galaxy, so visual effects should not introduce unnecessary performance overhead.
Solving Riddles
Solving riddles is an important part of the TreasureLink Mini experience. It gives players a chance to think creatively, interpret clues, and discover what they need to do next. Instead of simply following the treasure map, players must use their problem-solving skills to progress through the adventure.
The goal is to make solving riddles enjoyable, intuitive, and rewarding while keeping the mysterious treasure-hunt atmosphere.
11.1 Displaying a Riddle
When players reach a stage that requires solving a riddle, the app should present the clue in a clear and engaging format. The riddle should be easy to read, with enough space between the text and the answer field.
The visual design could use a mysterious clue card, subtle gold highlights, and a dark background that matches the rest of the app. Small animations can make the experience more immersive without distracting players from the actual question.
11.2 Entering an Answer
Players should have a simple way to enter their answers and submit them for checking. The answer field and submission button should be clearly visible and comfortable to use on a mobile screen.
The app should handle empty answers appropriately and provide useful feedback instead of allowing confusing or incomplete submissions.
An illustrative Flutter text field might look like this:
This is an example of the interface only. It does not implement answer checking or connect to the existing riddle system.
11.3 Checking Answers
When a player submits an answer, the app should compare it with the expected answer using the existing riddle logic.
If the answer is correct, the app should display a positive confirmation and allow the player to continue according to the expedition's rules. If the answer is incorrect, the app should explain that another attempt is needed and allow the player to try again.
Answer checking should be consistent and predictable. If the existing system supports ignoring differences in capitalization or unnecessary spaces, that behavior should be preserved.
11.4 Connecting Riddles to Checkpoints
Riddles should work together with the checkpoint system. Solving a riddle may complete a checkpoint, reveal another clue, or unlock the next stage, depending on the existing expedition design.
When a riddle is solved successfully, the app should update the appropriate progress information. It should not accidentally mark unrelated checkpoints as completed or reset the player's existing progress.
11.5 Saving Riddle Progress
Players should not have to repeat completed riddles simply because they close and reopen the app. TreasureLink Mini already uses SharedPreferences to store completed progress through the completed key.
The existing storage logic should be checked to confirm that successful riddle completion is recorded correctly and restored when the app starts again. Any changes should remain compatible with the current progress system.
11.6 Making Riddles Feel Rewarding
Solving a riddle should feel like a meaningful achievement. A short success animation, a subtle glow, or a brief message revealing the next step can make the experience more satisfying.
Incorrect answers should receive gentle, clear feedback rather than harsh error messages. Animations should remain lightweight so the app runs smoothly on the Samsung Galaxy.
The overall experience should combine clear instructions, reliable answer checking, consistent progress tracking, and a mysterious visual style.
Scanning QR Codes
TreasureLink Mini uses the mobile_scanner package to let players scan QR codes during an expedition. Scanning a code can connect a physical checkpoint to a clue or another stage of the treasure hunt.
12.1 QR Scanner
The scanner uses the phone's camera to detect QR codes.
12.2 Handling Scanned Codes
The app should validate scanned codes and respond appropriately to valid or invalid results. It should also handle camera permissions and scanning errors.
Any visual improvements should preserve the existing QR-scanning functionality and checkpoint logic.
GPS and Location Tracking
TreasureLink Mini uses the geolocator package to access the player's current location. GPS can help players understand where they are during an expedition, although accuracy depends on the device and surrounding environment.
The app should request location permission and handle cases where GPS is disabled or permission is denied.
The visual redesign should make location information easy to understand while preserving the existing GPS functionality. Since the treasure map is hand-drawn, GPS coordinates should not be plotted directly onto it without a suitable mapping or calibration system.
Tracking Player Progress
Tracking player progress is an important part of TreasureLink Mini because it allows players to see how far they have progressed through the expedition. As players complete checkpoints and solve riddles, the app should update their progress and make it clear which parts of the treasure hunt are finished and which remain.
14.1 Recording Completed Checkpoints
The app already uses SharedPreferences with the key completed to store progress. The updated implementation should preserve this existing system rather than introducing a separate progress-tracking mechanism.
For example, a list of completed checkpoint identifiers could be saved like this:
Here, completedItems represents the list of completed items. The actual data type and structure must match the existing implementation.
14.2 Displaying Progress
The Player Mode interface should show progress in a simple and visually appealing way. Completed checkpoints could have a distinct marker, while incomplete ones remain clearly identifiable.
A progress indicator can also help players understand their overall progress.
This function returns a value between 0.0 and 1.0, suitable for a Flutter LinearProgressIndicator or similar component. The counts should come from the actual expedition data.
14.3 Restoring Progress
When the app is reopened, previously completed checkpoints and riddles should remain completed.
The app should use the restored data to update the checkpoint markers and progress display. Existing reset functionality must also continue to work correctly.
The key requirement is that progress should remain consistent across app restarts without accidentally modifying or deleting the saved treasure map.
Completing the Treasure Hunt
Completing the treasure hunt should feel like the final achievement of the player's adventure. Once all required checkpoints and riddles have been completed, the app should recognize the completion and present a satisfying ending.
15.1 Detecting Completion
The app should determine whether all required checkpoints have been completed. This check must use the actual checkpoint list and existing progress data rather than relying on a fixed number of checkpoints.
For example:
This is an illustrative example. The real implementation should account for the expedition's existing completion rules, including any riddles or other requirements that must be satisfied.
15.2 Showing the Completion Screen
When the expedition is complete, the app should display a dedicated success screen or dialog. It could include a congratulatory message, a treasure-themed illustration, and a short animation.
The completion screen should match the app's mysterious adventure theme. Gold highlights, glowing effects, and a treasure-chest illustration could make the ending feel rewarding without overwhelming the interface.
The message should be clear and readable, especially on smaller screens.
15.3 Preventing Duplicate Completion Events
The completion screen should not repeatedly appear every time the interface rebuilds. The app should manage the completion state carefully and show the ending at the appropriate moment.
If progress is saved, the app should also restore the correct completion state when reopened. Any reset action should follow the existing rules for resetting player progress.
15.4 Starting Another Expedition
If the current app design supports resetting or preparing another expedition, the completion screen can provide a clear way to return to the relevant screen.
However, resetting progress should not automatically delete the organizer's saved map unless that is explicitly intended. Map storage and player progress must remain separate.
The objective is to provide a satisfying ending while preserving the existing navigation, persistence, and reset behavior.
App Design and Visual Style
TreasureLink Mini should feel like a mysterious treasure-hunting adventure. The visual design should support exploration, discovery, and problem-solving while keeping the app easy to use.
The redesign should improve the entire application rather than changing only the home screen. Organizer Mode, Player Mode, map viewing, QR scanning, riddles, and completion screens should all follow the same visual direction.
16.1 Color Palette
The existing theme provides a strong starting point:
- Gold — #FFC66D: Primary highlights, important actions, and treasure-related details.
- Teal — #39E5C1: Interactive elements, secondary highlights, and success indicators.
- Background — #061119: Main application background.
- Panel — #101F2A: Cards, dialogs, and content panels.
- Muted text — #9EB3BC: Supporting information and secondary labels.
These colors should be used consistently across the app. Text and icons must maintain sufficient contrast against their backgrounds.
16.2 Typography
Choose fonts that create an adventurous atmosphere without sacrificing readability. A distinctive font can be used for titles and expedition headings, while a simpler font should be used for instructions, riddles, buttons, and other information.
For example, Flutter's theme can define separate styles for headings and body text:
This example defines the core theme colors. It should be integrated with the existing theme instead of replacing other required settings without checking them.
16.3 Layout and Navigation
The layout should make the most important actions easy to find. Buttons should have clear labels, enough touch space, and consistent styling.
Organizer Mode should focus on preparing the expedition and drawing the map. Player Mode should prioritize viewing the map, finding checkpoints, scanning QR codes, and solving clues.
Avoid unnecessary visual clutter. Decorative elements should support the experience rather than compete with the map or instructions.
16.4 Consistency Across Screens
All screens should feel as though they belong to the same application. Use consistent spacing, corner radii, typography, icons, button styles, and animation behavior.
The redesign should also preserve the app's existing functionality. Changes to the layout must not break freehand drawing, map persistence, GPS, QR scanning, riddles, checkpoint tracking, or reset dialogs.
Images, Fonts, Icons, and Animations
Images, typography, icons, and animations can make TreasureLink Mini feel much more immersive. These assets should be chosen to support the treasure-hunting theme and improve the user experience, rather than being added purely for decoration.
17.1 Images and Illustrations
Use suitable images or illustrations for elements such as treasure chests, mysterious clues, ancient maps, expedition introductions, and successful completion screens.
The images should have a consistent visual style. Avoid mixing unrelated illustration styles or using large decorative images that make important controls difficult to see.
Organize the image files into a clear asset directory, for example:
These are suggested filenames, not existing project assets. Any new images must actually be created or included in the final project.
17.2 Custom Fonts
Choose fonts that match the adventure theme. Titles can use a more distinctive typeface, while body text should remain easy to read on a mobile screen.
If custom fonts are added, include the actual font files and register them in pubspec.yaml.
AdventureFont and the filename are illustrative. The configuration must match the actual font files included in the project.
17.3 Icons
Use a consistent set of icons for actions such as drawing, saving, editing, scanning QR codes, viewing location, opening clues, and resetting progress.
Icons should communicate their purpose clearly. Avoid mixing many different icon styles or using symbols that players might misunderstand.
Where appropriate, combine icons with text labels, especially for important actions that users may not recognize immediately.
17.4 Animations and Transitions
Use subtle animations to make interactions feel responsive. Suitable examples include:
- Smooth transitions between screens.
- Gentle highlights when a checkpoint is completed.
- Small animations when a riddle is solved.
- A reveal animation for the final treasure-hunt completion screen.
- Subtle feedback when buttons are pressed.
Animations should not slow down drawing or scanning, interrupt GPS updates, or delay important actions.
17.5 Asset Management
Update pubspec.yaml carefully whenever new assets or dependencies are introduced. Verify that every referenced file exists and that asset paths match their actual locations.
Prefer appropriately sized images and lightweight animations. The final application should remain responsive on the Samsung Galaxy, including during map drawing and other interactive activities.
Data Storage and Saving Progress
TreasureLink Mini needs to preserve important information between app sessions. This includes the organizer's hand-drawn map and the player's completed checkpoints or riddles.
The existing application uses SharedPreferences for local persistence. The redesign must preserve this behavior and avoid unintentionally changing existing storage formats.
18.1 Saving the Treasure Map
The organizer's map should be saved so it can be restored later. The existing map-storage key is intended to be separate from player progress.
If the current implementation stores map data as JSON, the app should continue to serialize and deserialize it using the existing data structure.
The implementation must preserve the actual drawing information needed to recreate the map, rather than saving only a screenshot if editable strokes are required.
18.2 Saving Player Progress
The existing progress-storage key is:
Completed checkpoint and riddle information should be saved using the data structure already used by the application.
When a player completes an activity, the app should update the stored progress without overwriting unrelated information.
18.3 Keeping Data Separate
The map and player progress serve different purposes and should remain independent. Updating or restoring the map must not accidentally reset completed checkpoints.
Likewise, resetting player progress should not delete the organizer's map unless the user explicitly chooses an action that is intended to remove it.
18.4 Loading and Handling Missing Data
The app should handle situations where no map has been saved, progress is empty, or stored data cannot be decoded.
For example:
This example demonstrates retrieving stored values. The map-loading logic must still decode and restore the map using its actual format.
18.5 Resetting Data Safely
Any reset dialog should explain what will be reset before the user confirms. If the existing reset feature clears only player progress, preserve that behavior.
Avoid clearing all SharedPreferences values indiscriminately, because doing so could delete the saved map or other important settings.
App Performance and Compatibility
The updated application should look polished while remaining responsive on the Samsung Galaxyrunning Android 11. Visual improvements should not introduce excessive memory usage, slow animations, or unnecessary delays.
19.1 Image and Animation Performance
Use image sizes appropriate for their display dimensions. Avoid loading unnecessarily large images or using complex effects on every screen.
Animations should be short, efficient, and purposeful. The freehand map-drawing experience is especially important because lag can make drawing frustrating.
19.2 Map Rendering
The map should continue to render smoothly as the organizer draws. The implementation should avoid unnecessary work during every pointer movement and should preserve the original strokes when switching between Organizer Mode and Player Mode.
If the current app uses CustomPainter, inspect its repaint behavior and data structure before making changes.
19.3 Dependency Management
The existing project uses packages including:
- geolocator for location access.
- mobile_scanner for QR-code scanning.
- shared_preferences for local data persistence.
Keep existing dependencies unless there is a clear reason to change them. If new packages are needed for animations, fonts, or other visual improvements, check their compatibility with the project's Flutter version and Android configuration.
19.4 Android Permissions
Check that location and camera permissions continue to work correctly. The app should explain or handle denied permissions gracefully instead of crashing or leaving players stuck on a screen.
Do not request permissions that the app does not need.
19.5 Responsive Layout
Test the interface at different screen sizes and text scales. Buttons, dialogs, riddles, and map controls should remain usable without clipping or overlapping.
The design should prioritize reliable functionality over complicated visual effects. TreasureLink Mini must remain practical to use during a real outdoor expedition.
Testing and Fixing Issues
After making the visual and functional improvements, the complete project should be checked to ensure that existing features still work correctly. A redesign is not complete if the application looks better but loses important functionality.
20.1 Inspecting the Project
Before editing files, review the project structure, existing Dart files, pubspec.yaml, asset directories, and Android configuration.
Identify how the current map, progress, QR scanner, GPS, riddles, and reset functionality are implemented. Preserve working code wherever possible instead of replacing entire files without understanding their dependencies.
20.2 Testing Core Features
Test the following features individually:
- Organizer Mode opens correctly.
- Freehand map drawing responds smoothly to finger movement.
- Map saving and restoration preserve the original drawing.
- Player Mode displays the saved map.
- GPS permissions and location updates work appropriately.
- QR scanning recognizes codes and handles invalid results.
- Riddle answers are checked correctly.
- Checkpoint completion updates the player's progress.
- Progress remains available after restarting the app.
- Reset dialogs behave as intended without deleting unrelated data.
- Images, fonts, icons, and animations load correctly.
20.3 Running Flutter Checks
Run the following commands from the project's root directory in Windows CMD:
flutter pub get retrieves the required dependencies, flutter analyze checks for code issues, and flutter run launches the application on a connected device or available emulator.
Resolve important errors and warnings introduced by the changes. If an issue cannot be fixed, document it clearly rather than claiming that the application has been fully tested.
20.4 Testing on the Physical Device
Test the application on the Samsung Galaxy running Android 11 whenever possible.
Pay particular attention to camera access, location permissions, drawing responsiveness, screen transitions, memory usage, and persistence after closing and reopening the application.
Also test situations such as denied permissions, missing saved maps, empty progress, and invalid QR codes.
20.5 Final Verification
Before delivering the project, verify that all required assets are present, pubspec.yaml references the correct files, and the app builds successfully.
The final result should preserve existing functionality while providing a more cohesive and immersive adventure experience.
Future Improvements
Once the current version is stable, TreasureLink Mini could be expanded with additional features that make expeditions more flexible, engaging, and easier to organize.
These ideas should be treated as optional future improvements. The current app should remain the priority, and new features should not interfere with the existing implementation.
21.1 Exporting and Sharing Maps
A future version could allow organizers to export a prepared treasure map and share it with players using separate devices.
Possible approaches include exporting structured map data, generating a QR code containing suitable data, or using an online service to synchronize expedition information.
Because SharedPreferences stores data locally, cross-device sharing would require an additional mechanism.
21.2 Customizable Expeditions
Future versions could allow organizers to customize checkpoint names, clues, riddles, and expedition details. A more flexible setup process could make the app suitable for different events and locations.
21.3 Additional Riddle Types
The app could eventually support multiple kinds of challenges, such as multiple-choice questions, image-based clues, word puzzles, or riddles that reveal additional information after completion.
Each new challenge type should connect reliably to the existing checkpoint and progress system.
21.4 Improved Expedition Features
Other possible improvements include better map editing tools, additional checkpoint markers, more flexible progress displays, and optional hints for difficult riddles.
Any feature involving real-world positioning should account for GPS accuracy and the fact that the organizer's map is hand-drawn.
21.5 Keeping Future Development Practical
Future features should be added gradually, with testing after each significant change. The application should remain lightweight and compatible with the intended Android devices.
The goal is to build on the existing foundation rather than adding features that make the app unnecessarily complicated.
Final Project Files and Setup Instructions
The final deliverable should be a complete, working TreasureLink Mini project that includes the visual improvements and preserves the existing functionality.
Claude should inspect the actual project files before making changes and provide all updated files required to run the application.
22.1 Required Project Files
The final project should include:
- All updated Dart source files.
- The updated pubspec.yaml.
- Every new image, font, icon, or other asset used by the app.
- Any necessary Android permission or configuration changes.
- Supporting files required to build and run the application.
Do not reference assets or packages that are missing from the delivered project.
22.2 Installing Dependencies
After obtaining the updated project, open Windows CMD and navigate to the project directory.
For example, if the project is stored at C:\Users\abc\Desktop\TreasureLinkMini, use:
The directory in this example should be replaced with the actual project location.
22.3 Checking and Running the Application
Before running the app, analyze the source code:
Then connect the Samsung Galaxy with USB debugging enabled and check that Flutter detects it:
Finally, launch the app:
These commands assume Flutter and the Android development tools are correctly configured.
22.4 Final Delivery Requirements
The final response should explain what was changed, identify any new dependencies, and provide clear setup and testing instructions.
If files were modified, provide the complete updated files or the complete project in a form that can be used directly. Avoid incomplete snippets that require the user to guess where the remaining code belongs.
Most importantly, verify that the final project preserves the organizer's map drawing, map persistence, Player Mode, GPS, QR scanning, riddles, checkpoint tracking, saved progress, and reset functionality.
The final goal is a visually polished, immersive, and reliable TreasureLink Mini application that can be built and tested on the target Android device.