Production Roadmap

A structured, phased execution plan to transition WeatherAPP Libre to a compliant, stable, and production-ready release.

Executive Summary

WeatherAPP Libre is a private, ad-free weather and natural-light planner for photographers and outdoor users, featuring selectable forecast models and zero GPS tracking. To reach production readiness, we executed a massive architectural refactoring to a modular system, rebuilt the solar and lunar engines via a 17-module almanac-grade remediation, and successfully integrated official multi-provider alerts (ECCC Datamart and MeteoAlarm).

Production Readiness Assessment

This metric tracks our proximity to a full public release. All critical deployment blockers—including official CAP-CP alert sourcing, Open-Meteo licensing, and multi-provider alert state management—have been cleared. Core infrastructure, including the 17-module astronomical engine overhaul, R8 release optimization, and a hardened automated test suite, is fully deployed and verified.

Product Concept9.0/10
Privacy Posture10/10
Feature Depth10/10
Visual Identity9.5/10
Weather Data Handling9.5/10
Architecture10/10
Astronomical Accuracy10/10
Alert Integrity10/10

1. Phase 1: Trust, Safety & Compliance

1.1 Alert Integrity Remediation

  • Remove all synthetic model-derived severe weather conditions masquerading as official alerts.
  • Implement official alert sourcing via a verified CAP-CP feed, preserving original identifier, issuer, timestamp, severity, and expiry.
  • Execute the CAP-CP agent prompt to finalize background WorkManager polling, XML parsing, and polygon/circle matching.
  • Resolve Alert Log persistence bug to ensure synthetic test alerts and historical CAP entries are correctly retained and displayed.
  • Architect a modular alert provider pipeline (AlertProviderRouter) to support multiple international meteorological networks.
  • Integrate the MeteoAlarm network for comprehensive European weather alerts, including strict geographic gating and system-level push notifications.
  • Replace deprecated ECCC Atom feeds with a modern Datamart directory scraper that parses CAP-CP XML directly.

1.2 Astronomical Data Validation

  • Rebuild the astronomical dataset from documented, authoritative sources (Jean Meeus).
  • Implement automated validation to reject impossible phase intervals.
  • Store event times in UTC and include visibility regions where applicable.
  • Replace placeholder lunar azimuth calculations with iterative topocentric root-finding.
  • Execute a 17-module almanac-grade remediation of the solar and lunar engines, integrating official Espenak/Meeus Delta T polynomials, correcting atmospheric refraction frames, and upgrading topocentric math for polar stability.

1.3 Licensing and Attribution Compliance

  • Update UI attribution to dynamically reflect the active forecast model (e.g., "Data: DWD via Open-Meteo").
  • Publish comprehensive Licenses & Sources page detailing all data providers and open-source libraries.
  • Formalize the commercial-use arrangement with Open-Meteo to ensure compliance with their pricing and terms of service (resolved via GPLv3 open-source publication).

2. Phase 2: Core User Value & Accuracy

2.1 Calculation and Display Refinements

  • Correct solar-noon elevation to account for the absolute difference between latitude and solar declination.
  • Implement explicit "NeverOccurs" or "AlwaysAboveThreshold" states for polar night and midnight sun, avoiding artificial midnight boundary clamping.
  • Refactor solar display to focus on azimuth angles rather than duplicating sunrise/sunset times.
  • Remove the unreliable "Ceiling" metric entirely from the UI and data models.
  • Refine UI consistency with alphabetized System settings, unified 16dp dialog corner radii, and proper system bar margin handling.

2.2 High-Value Feature Additions

  • Ensure all themes pass accessible contrast ratio testing and include a reduced-motion option.
  • Integrate a 36-hour Hourly Forecast with expandable stat panels and theme-reactive surfaces.
  • Replace all weather condition emojis with a custom, theme-reactive 28-state vector icon set.
  • Restructure inline sub-tabs into Current, Hourly, and Natural Light categories.
  • Implement 7-Day Forecast placement control (inline vs. dropdown menu) and a comprehensive Menu Organization screen (drag-to-reorder, visibility toggles, default launch page, separators).
  • Create and integrate a comprehensive in-app User Manual accessible from the navigation drawer and Info screen.
  • Implement visible "last refreshed" and "cached data" indicators via Hero Card metadata popup and a dedicated Cached Data Inspector screen.
  • Develop a home-screen widget for immediate at-a-glance utility.
  • Implement French localization to serve the Canadian market effectively.

3. Phase 3: Technical Architecture & Stability

3.1 Architectural Decoupling

  • Decompose the monolithic MainActivity into focused components (ThemeManager, WeatherDisplayManager, AstronomyDisplayManager, LocationTabsManager, etc.).
  • Decompose activity_main.xml into composed section layouts to eliminate deep LinearLayout nesting.
  • Convert repeated hand-written metric cells into a RecyclerView grid backed by an adapter.
  • Unify alert caching and UI rendering under a single GlobalAlertCache and UnifiedAlert model, eliminating legacy provider-specific state management.

3.2 Testing Matrix Implementation

Establish automated test coverage for the following edge cases:

  • Daylight-saving transitions and Saskatchewan's non-DST behavior.
  • Locations east and west of the International Date Line.
  • Southern Hemisphere solar noon and Arctic summer/winter extremes.
  • Malformed XML records and impossible lunar-phase sequences.
  • Topocentric lunar parallax, horizon dip, and atmospheric refraction edge cases.
  • Curate and harden unit test suite, removing diagnostic scaffolding and enforcing deterministic invariants.

4. Phase 4: Release Preparation & Compliance

4.1 Privacy and Store Compliance

  • Publish a comprehensive privacy policy detailing data transmission (latitude/longitude to Open-Meteo, IP metadata, geocoding terms).
  • Ensure the Google Play Data Safety declaration accurately reflects the absence of advertising, analytics, and GPS tracking SDKs.
  • Standardize website navigation, typography, and layout across Home, About, Licenses, and Roadmap pages.
  • Enable R8 code shrinking, obfuscation, and resource optimization for release builds to meet Play Console DEX optimization requirements.
  • Externalize all hardcoded UI strings to strings.xml to establish a comprehensive localization infrastructure.
  • Publish application source code under the GNU GPLv3 with explicit trademark reservation for the WeatherAPP Libre brand.
  • Implement a "Clear All Cache" control within the Data Cache settings via the new Cached Data Inspector.
  • Implement a one-tap "Delete local app data" (full factory reset of preferences) control within the application settings.
  • Implement strict opt-in consent enforcement for background alert monitoring across all integrated meteorological networks.
  • Localize the multi-provider alert consent dialog into English and French.

5. Phase 5: Advanced Features & Expansion

With the core architecture stabilized, development shifts to high-value utility features, intelligent data routing, and advanced astronomical tracking.

5.1 Diagnostic Logging Dashboard

  • Build an in-app Logs screen accessible via the navigation drawer.
  • Implement an internal event logger for lifecycle, cache, and resolution events.

5.2 Lunar Utility Pages

  • True Dark Sky Window: Calculate periods of astronomical darkness overlapping with low lunar interference.
  • Night Visibility Forecast: Estimate ambient light potential based on moon phase, altitude, twilight, and cloud cover.
  • Solunar Activity Forecast: Display traditional major/minor solunar periods based on lunar transit and nadir.
  • Lunar Calendar: Comprehensive week-by-week lunar phase tracking, inline event expansion, 3-year special event caching, and atmospheric phenomena heuristics (Moonbows, Halos, etc.).

5.3 Meteor Shower Tracking (On-Device)

  • Hardcode a lightweight database of major annual meteor showers (orbital parameters, peak dates, radiant coordinates).
  • Use existing topocentric algorithms to calculate radiant Altitude/Azimuth for the user's specific location.
  • Cross-reference radiant altitude with True Dark Sky and Night Visibility data to generate an on-device "Meteor Viewing Score".

5.4 Aurora & Space Weather Forecast

  • Integrate the NOAA Space Weather Prediction Center (SWPC) API to fetch real-time Kp index and solar wind data.
  • Calculate the user's geomagnetic latitude on-device to determine auroral oval reach.
  • Overlay geomagnetic storm data with existing cloud-cover cache to provide a localized "Clear Sky Aurora Probability".

5.5 Extension Ecosystem

  • Finalize and publish the declarative extension manifest schema (v1) for themes and forecast providers.
  • Build and deploy the community extension catalog API and submission workflow at weatherapplibre.ca.
  • Implement the in-app extension browser, downloader, and manifest validator.

5.6 Global Alert Expansion

  • Leverage the newly established AlertProviderRouter to integrate the US National Weather Service (NWS) CAP feed for American locations.
  • Investigate and integrate the Bureau of Meteorology (BOM) feed for Australian locations.
  • Implement automated regional provider routing based on user-selected location country codes.

6. Production Release Gates

The application must not proceed to public release until the following non-negotiable criteria are met and verified by QA:

Completed Release Criteria:
  • Official ECCC CAP-CP alert pipeline is fully implemented, tested end-to-end, and strictly truthful (zero synthetic alerts).
  • Modular multi-provider alert architecture deployed, supporting both ECCC (Datamart) and MeteoAlarm networks with strict coordinate-scoped state management.
  • Comprehensive automated test suite passes consistently across all architectural modules.
  • All hardcoded UI strings are externalized to strings.xml to support future localization.
  • DEX code optimization and R8 obfuscation enabled for release builds.
  • Open-Meteo licensing formally resolved via GPLv3 open-source publication.
  • Astronomical calculation engines hardened via 17-module remediation and validated by automated regression tests.

Note: Core architecture refactoring, astronomical data validation, layout decomposition, accessibility compliance, baseline privacy compliance, and official multi-provider alert integrity have been satisfied and are no longer blocking release gates.

7. References and Compliance Sources

Note: Pricing, platform rules, API terms, and competitor offerings are subject to change. Reverify all linked sources prior to final release.