Behavior across the TripLens app. Settings are stored locally on this device. TripLens v3.4
Day Planner behavior and source-list defaults.
Enables dragging place cards into day buckets and reordering planned places.
Shows the older manual ordering and day assignment controls as a fallback if drag-and-drop has problems.
Allows one saved Place to appear in multiple day plans by creating separate DayPlanItem records that reference the same Place.
Reserved for a future warning when the same Place is added more than once to the same day. For now, duplicates are allowed.
Initial value of the Day Planner View Mode dropdown on page load. During the session, manual changes to View Mode are preserved. On the next reload this default is reapplied.
When viewing a day on the map, zones planned for that day get a numbered marker and join the route line. Turn off to keep zones as dashed circles only.
In day-route view, numbered markers use the day color as outline and the place's category color as fill. Turn off to use the day color everywhere.
Global toggle for in-app motion. Controls Day Planner drop-preview shifting today, and will gate future animation features. When off, non-animated affordances (e.g. drop indicator line) still render.
Restore baselines for testing. These actions cannot be undone.
Clears all planned visits, day assignments, and order/route state for the selected trip. Saved places, zones, categories, base location, settings, and other trips are preserved.
Restores all trips, places, zones, categories, and planner data to the seeded demo baseline. All generated/test data on this device will be discarded.
How place lookups and imports are handled.
The app first analyzes the input to extract structured clues such as place name, address, search query, and coordinates. It then sends the best query to OSM and normalizes the result. This is the default strategy.
Allows the app to detect and parse Google Maps URLs before sending a query to the resolver.
Allows the app to use OpenStreetMap/Nominatim as the main place lookup provider.
Allows the resolver pipeline to use a non-default experimental web provider when the selected strategy requires it. Default OFF. When OFF, the experimental provider never runs — even in the Debug Console. Does not affect the normal OSM/parser flow.
If the main resolver result has confidence below this value, fallback/enrichment providers may be used when enabled.
Diagnostic tools. Off by default.
Enables internal debugging tools and additional diagnostic output.
Shows the parser and resolver output for place imports/searches.
Shows raw provider response data for debugging. Does not show secrets or API keys.
Saves recent resolver traces locally so they can be copied and inspected.
Shows the current day planner state for debugging drag-and-drop and ordering issues.
Fine-grained controls for in-app motion. Most users can leave these at defaults.
How far Day Planner cards shift to open a gap during a drag. Requires "Enable animations" to be on. When animations are off, this behaves as 0 and the non-animated drop indicator still renders.
Placeholders for upcoming providers.
Future optional provider for official place lookup and enrichment. API keys will be configured through secure backend secrets, not stored in normal app settings.