Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create an editable mobile-first app prototype using the existing project stack for [PROJECT] and [AUDIENCE]. The task is: Offline Hiking Journal.
Required content and structure
Record a trail entry with a photo and optional location, save it on the device, then show exactly which entries are waiting to sync.
Screens and navigation
Build three connected views: Trips; New entry; Sync queue. Keep the selected record visible in the screen title or summary. Support an explicit back action and preserve in-progress inputs when moving between views. Keep the primary action near the relevant content and account for mobile safe areas, a visible software keyboard and long translated labels. At desktop widths, adapt the composition without removing a step or changing the task.
Project inputs
Use [APPROVED_CONTENT] for names, records, labels, quantities and destinations. Ask for missing data instead of inventing operational claims. Demonstration records may use the fictional brand Field Notes; label these as sample data. Explain which actions are local prototype interactions and which would require authentication, persistence, permissions or a backend. Do not connect external services or claim a transaction was completed unless that integration has been explicitly implemented and tested.
Design direction
Follow [BRAND_RULES]. When no brand is supplied, use warm ivory, forest green, outdoor photography. Make the workflow recognizable through its own content and controls, rather than repeating generic dashboard cards. Use a consistent spacing scale and clear text hierarchy. Include visible keyboard focus, accessible names, sufficient contrast and non-color status labels. Respect reduced motion and keep animated transitions optional.
Task-specific acceptance check
- A saved text note must stay available when its photo upload fails; distinguish local save from completed sync.
Interaction states
Implement the three-screen happy path with local sample data. Include a useful empty state, validation before completing an action, a loading or pending state and a recoverable failure state. Destructive changes require a review or undo path. Keep the state of a record consistent across all three views. Do not silently discard partially completed input or change a user's choice after a retry.
Delivery and review
Return the editable app views and explain the data model, any local storage behavior and unimplemented integrations. Test at 320px and a wider viewport, with keyboard navigation and long content. Use the task-specific acceptance check above to review the result before adding features. Keep demonstration behavior clearly distinct from a running production service.
Reference attachment and reconstruction goal
Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.
Reference composition and content
Use the attached reference.webp as the visual reference for Offline Hiking Journal. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Record a trail entry with a photo and optional location, save it on the device, then show exactly which entries are waiting to sync. Use the following task-specific layout guidance when translating the image into editable elements: Begin with Trips as the entry screen, give New entry a clear primary action, and make Sync queue explain what happened and what can happen next. Use warm ivory, forest green, outdoor photography as a starting direction, adapting it to the supplied brand. Keep record identity and navigation context visible across the three screens. Prioritize thumb-accessible controls and readable labels over decorative panels; on wider screens, keep the workflow coherent rather than stretching a mobile composition edge to edge.
Visual direction from the example brief
Begin with Trips as the entry screen, give New entry a clear primary action, and make Sync queue explain what happened and what can happen next. Use warm ivory, forest green, outdoor photography as a starting direction, adapting it to the supplied brand. Keep record identity and navigation context visible across the three screens. Prioritize thumb-accessible controls and readable labels over decorative panels; on wider screens, keep the workflow coherent rather than stretching a mobile composition edge to edge.
Interaction specification
The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your project and build the connected flow: Record a trail entry with a photo and optional location, save it on the device, then show exactly which entries are waiting to sync. A saved text note must stay available when its photo upload fails; distinguish local save from completed sync. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.
Visual comparison and delivery
- Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write an Offline Hiking Journal Design Prompt
Use this offline hiking journal design prompt to record a trail entry with a photo and optional location, save it on the device, then show exactly which entries are waiting to sync.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Connect Trips, Entry and Sync Status
Trips is selected in a segmented navigation bar on the left. The center view is titled “New entry”; the right view is titled “Sync queue” and leads with a connection message. Warm ivory surfaces and forest-green controls connect the screens without making all three layouts identical.
Name the views and their responsibilities before describing color or decoration. The reference places them side by side to show the sequence; the implemented mobile app should move between them, not squeeze all three into one phone viewport. Begin with Trips as the entry screen, give New entry a clear primary action, and make Sync queue explain what happened and what can happen next. Use warm ivory, forest green, outdoor photography as a starting direction, adapting it to the supplied brand. Keep record identity and navigation context visible across the three screens. Prioritize thumb-accessible controls and readable labels over decorative panels; on wider screens, keep the workflow coherent rather than stretching a mobile composition edge to edge.
From the Prompt
Build three connected views: Trips; New entry; Sync queue. Keep the selected record visible in the screen title or summary. Support an explicit back action and preserve in-progress inputs when moving between views. Keep the primary action near the relevant content and account for mobile safe areas, a visible software keyboard and long translated labels. At desktop widths, adapt the composition without removing a step or changing the task.
Make It Your Own
Build three connected views for [PROJECT]: Trips, New entry and Sync queue. Open a trip to see its entries; use the add action to start a draft associated with that trip. Give the editor an explicit back action that preserves the draft. Keep the same trip identity in the queue. Show one view at a time on mobile, with a deliberate wider-screen layout.
Define What an Entry Actually Stores
The entry screen combines a large photograph with a titled note, a character count, an optional location and a “Save on device” button. The location row has its own remove control. These are separate pieces of content, rather than one flattened image.
Turn the pictured fields into a small data contract. Decide what is required, what can be removed and what survives a failed photo upload. The visible character counter suggests a limit, but your brief must define the actual validation rule.
From the Prompt
Use [APPROVED_CONTENT] for names, records, labels, quantities and destinations. Ask for missing data instead of inventing operational claims. Demonstration records may use the fictional brand Field Notes; label these as sample data. Explain which actions are local prototype interactions and which would require authentication, persistence, permissions or a backend. Do not connect external services or claim a transaction was completed unless that integration has been explicitly implemented and tested.
Make It Your Own
Each entry stores a trip ID, title, note text, optional photo, optional coordinates and a local-save timestamp. Use [APPROVED_CONTENT] for sample entries. Let users remove the location without deleting their note. Define the note limit in [CONTENT_RULES], show the remaining count and explain validation inline. Saving must retain text even when the photo is unavailable.
Separate Local Save from Completed Sync
The queue distinguishes “Saved offline” from “Waiting for connection” using text as well as color. A banner explains the connection condition before the list. This communicates the intended state model, but the picture alone cannot prove that data persists or uploads resume.
Write the transition rules explicitly. Local save, queued upload and completed sync are different states. A recovery test should check both the text record and its attachment instead of treating the entry as a single all-or-nothing operation. Test this specific boundary first: A saved text note must stay available when its photo upload fails; distinguish local save from completed sync. Then run the main flow with a long record title, no saved records and a failed action. A user should be able to tell what is saved, what is pending and what can be undone without relying on color. Verify that returning to the previous screen preserves entered data and that a screen reader encounters the title, status and primary action in a sensible order.
From the Prompt
A saved text note must stay available when its photo upload fails; distinguish local save from completed sync.
Make It Your Own
After local save, show the entry immediately and mark its upload as pending. If the photo upload fails, retain the saved text and offer a retry for that attachment. Update queue counts from actual record state and prevent duplicate entries on retry. Do not show “Synced” until the implemented service confirms success; label simulated transitions as demo behavior.
Use the Reference and the Brief Together
Attach the reference image with the customized prompt in OpenDesign. Replace the relevant instructions with your project choices instead of appending conflicting directions. The example is an AI-generated visual concept. Connected services, device permissions and persistent data require separate implementation and testing.
- A saved text note must stay available when its photo upload fails; distinguish local save from completed sync.
- Test this specific boundary first: A saved text note must stay available when its photo upload fails; distinguish local save from completed sync. Then run the main flow with a long record title, no saved records and a failed action. A user should be able to tell what is saved, what is pending and what can be undone without relying on color. Verify that returning to the previous screen preserves entered data and that a screen reader encounters the title, status and primary action in a sensible order.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine only the New entry to Sync queue transition. A saved text note must stay available when its photo upload fails; distinguish local save from completed sync. Show the relevant pending, failure and completed states with explicit labels. Preserve the approved navigation, typography and other screens. Return the changed views and describe how entered data survives a retry.
