# JL7 Flutter App Notes This document records the general mobile app documentation pattern for JL7. It focuses on Flutter structure, iOS and Android support, navigation, release workflow, and maintenance checks. ### Overview JL7 is documented as a Flutter-based mobile app. The goal of this page is to give maintainers a clear reference for how the app is structured and what should be reviewed before updates are released. The keyword app is useful here because the page is about mobile app documentation. It should appear naturally in sections that discuss structure, navigation, testing, and release handling. ### App Purpose This page should help a developer, editor, or project maintainer understand the app at a practical level. It does not need to describe every file in the codebase, but it should explain the areas that affect future updates. A good app document should make it easy to understand the platform, the user paths that need testing, the screens that matter most, the release process, and where related access notes are documented. ### Flutter Project Structure The app should be documented around its real Flutter structure. If the project uses separate folders for screens, components, services, and assets, those should be described in a short, practical way. Avoid complex architecture language unless the project actually follows that pattern. For most maintenance documentation, plain names such as screens, widgets, assets, config, and services are easier to understand. ### iOS and Android Support Flutter allows shared development across iOS and Android, but both platforms still need separate review. Navigation, browser handoff, app permissions, keyboard behavior, and layout spacing can differ between devices. For Android-specific release notes, see the [PUB777 Android APK Release Notes](/sites/documentation/pub777.md). ### Navigation and Release Workflow The app should be reviewed from the first screen through the main action path. A maintainer should check whether navigation labels are clear, whether users can go back without losing context, and whether external links open in the expected place. A simple release review should cover Flutter dependencies, test devices, key screens, external links, access behavior if present, and whether release notes match the current build. Release notes should be short and specific. A maintainer should be able to tell what changed without reading promotional text. For access-focused app documentation, the [ZS777 Flutter App Access Notes](/sites/documentation/zs777.md) provide a closer reference. ### Project Reference Use [JL7 apps](https://jl7.digital/) as the current project reference when reviewing this page. Check whether the live page or access path still matches the app structure and release notes described here. ### Maintenance Notes Review this page after major UI changes, release-process changes, dependency updates, or navigation changes. Keep the document focused on what a maintainer can inspect and test. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://gametalk99.gitbook.io/sites/documentation/jl7.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.