LocationNotes for Android
The Android app is the field client for LocationNotes. It opens directly to the map, keeps note capture available when connectivity drops, and syncs back to the same LocationNotes website and API that power the public pages, account flows, and team workspaces.
Authentication API docs Support Browse public teams
Core Android workflow
- The app starts on the map so nearby context is visible first.
- Notes can be organized spatially on the map or structurally through hierarchical categories.
- Online and offline state stays visible in the app, including separate health for network, maps, and sync.
- Nearby public notes preload by area when the device is online.
- Categories, notes, and team context are stored with GUID-based identifiers for conflict-safe sync.
Offline-first behavior
LocationNotes is designed so field capture does not stop just because the network is unstable. The Android app keeps local note and category state on the device, queues writes for later sync, and lets a user keep working until the API is reachable again.
- Anonymous users may create private local notes on the device without a LocationNotes account.
- Those anonymous notes are device-local only until the user signs in and chooses to sync.
- Signed-in users can keep creating or editing eligible notes offline and push those changes during the next sync cycle.
- Team administration tasks, membership changes, invite-link changes, and public-page settings still require a live server connection.
Accounts, sync, and publishing
Authentication is required before the Android app can sync personal notes to the server, publish a note publicly, or participate in team workflows that depend on the shared server state. The same account can be used across the Android app and the website.
- Current public sign-in methods are local user name and password, Google, and Facebook. Recovery emails stay separate from the local sign-in identifier.
- New accounts are offered only to users age 16 and older, and older where local law requires it.
- Public note publishing and sync are blocked until the user is authenticated.
- Website account pages handle password changes, recovery email changes, linked-provider management, data export, and account deletion.
Notes, visibility, and teams
Notes in the Android app can stay private, be published publicly, or belong to a team. Team notes still follow the same visibility rule set used by the website and API: a team note can remain private to the owner plus current team members, or it can be public.
- Private personal notes are visible only to the signed-in owner.
- Private team notes are visible to the note owner and current active members of the associated team.
- Public notes can appear on public maps, profile pages, team pages, note pages, and public search results.
- When content is created in a specific language, the system records that content language and preserves it on public pages.
What still happens on the website
The Android app is not the whole product surface. The website hosts the public marketing pages, the public team directory, profile pages, public team pages, note pages, account security, exports, and delete-account workflows. Team page settings and most public-sharing administration also live on the website.
- Public search covers note titles, note bodies, and category names.
- Public teams lists public teams in the visitor's current language by default.
- Website public team lists plus the published note map/list on public profile or team pages default to the visitor's current website language, while public trackable and trackable-group lists stay multilingual so journey and logistics data remain complete.
- The saved stop is an immutable logistics snapshot. If a linked note later moves, the journey keeps the original snapped coordinate so the route history does not silently change.
- Trackable read models can also surface the current visible notes at that coordinate, so the route can stay accurate even when nearby notes later change.
- Place, history, and access stay separate: the journey stop preserves the snapped coordinate, the note keeps its own editable record, and the note's visibility plus required access scope decides who can open note content.
- Visitors can switch website languages or use explicit all-language search when they want to browse another authored language.
- Authentication documents callback URLs and sign-in behavior.
- Privacy and Terms explain public pages, team rules, exports, and deletion.
Beta builds
Android beta access is managed through the Beta Testers team. Signed-in team members can open the beta page for the current APK, and everyone else can review the team page or request access there.
Single deployment model
LocationNotes publishes the website and API together as one ASP.NET Core server artifact. The Android app points to that same domain for authentication, sync, public-note loading, and public content discovery. Use the API docs when you need the exact routes and JSON examples instead of the website walkthroughs.