Description
According to the attached screenshots, the June app currently does not use the modern edge-to-edge rendering mode on Android.
Visually, the app relies on a legacy approach — likely fitsSystemWindows or a statically colored navigation bar. As a result, an opaque bar (the navigation bar background) appears at the bottom of the screen, overlapping the content instead of being drawn transparently over it.
Current behavior:
- The app window is shifted or cropped to avoid the system bars.
- An opaque bar is visible at the bottom of the screen where the navigation bar sits, overlapping the UI.
- Content does not flow behind the status bar or navigation bar, making the interface look outdated and "stepped."
Expected behavior (modern standard):
According to Google's recommendations, a modern Android app should support edge-to-edge:
- Transparent system bars — both the status bar and navigation bar should be transparent.
- Content behind bars — the main app content draws behind the system bars, not next to them.
- Proper insets — interactive elements (buttons, list items) must receive correct padding so they are not obscured by the system UI (e.g., the gesture bar at the bottom), while the app background extends edge to edge.
Why this is important
Google started recommending the edge-to-edge mode with Android 10 (API 29), when gesture navigation was introduced. The official documentation states:
"Starting in Android 10 (API level 29) and above, apps can draw content edge-to-edge, using the full screen area. System bars (status bar and navigation bar) should be transparent, and content should draw behind them with proper inset handling."
Starting with Android 15 (API 35), this mode becomes the default behavior for all apps, even if the developer does not explicitly call enableEdgeToEdge(). If an app is not ready for edge-to-edge, the system will forcibly enable it anyway — this leads to visual issues: the opaque navigation bar may overlap content even more, or insets become incorrect.
Migrating June to edge-to-edge will:
- Remove the opaque bar at the bottom — the interface will use the full screen area, and system bars will become transparent.
- Align with modern Android standards (Material Design, Android 15+).
- Avoid breakage in future Android versions when the legacy mode is no longer supported.
Screenshots


Description
According to the attached screenshots, the June app currently does not use the modern edge-to-edge rendering mode on Android.
Visually, the app relies on a legacy approach — likely
fitsSystemWindowsor a statically colored navigation bar. As a result, an opaque bar (the navigation bar background) appears at the bottom of the screen, overlapping the content instead of being drawn transparently over it.Current behavior:
Expected behavior (modern standard):
According to Google's recommendations, a modern Android app should support edge-to-edge:
Why this is important
Google started recommending the edge-to-edge mode with Android 10 (API 29), when gesture navigation was introduced. The official documentation states:
Starting with Android 15 (API 35), this mode becomes the default behavior for all apps, even if the developer does not explicitly call
enableEdgeToEdge(). If an app is not ready for edge-to-edge, the system will forcibly enable it anyway — this leads to visual issues: the opaque navigation bar may overlap content even more, or insets become incorrect.Migrating June to edge-to-edge will:
Screenshots