Product Requirements Document

MyWeather Motion is an Android weather application built using MIT App Inventor. It presents current conditions, location-aware forecasts, worldwide city search, a three-day outlook and a polished animated weather dashboard. The application combines App Inventor blocks with a locally bundled HTML/CSS/JavaScript interface displayed through WebViewer.

Document status: Draft requirements based on the preserved MyWeather project and preview. This is a product specification, not evidence that every release acceptance test has passed.

Users often need to decide what to wear, whether to carry an umbrella and how the weather may change over the next few days. Weather apps that bury the essentials behind multiple screens create unnecessary work.

MyWeather brings location, conditions, forecast, and weather highlights into a single mobile-first dashboard with animated visual cues. City search also keeps the experience useful when GPS is unavailable or not permitted.

• Clarity: current temperature, condition, place and update state are immediately understandable.
• Utility: GPS and city search can both lead to a weather forecast.
• Consistency: Celsius/Fahrenheit selection persists between sessions where storage is available.
• Resilience: missing permission, unavailable city results and network errors have usable feedback.
• Accessibility: primary content is readable on common Android phone sizes and interactive targets are easy to tap.

Suggested measurement plan (targets to be agreed): task completion for city search and unit switching; API-error recovery rate; launch-to-forecast time; crash-free sessions; permission-denial completion rate. No fabricated production KPIs are used.

• US-01 As a user, I want to use my location so that I can see local weather.
• US-02 As a user, I want to search for another city so that I can plan for travel.
• US-03 As a user, I want temperature, sky condition and feels-like values so that I can dress appropriately.
• US-04 As a user, I want humidity, wind and precipitation data so that I can prepare for daily conditions.
• US-05 As a user, I want a three-day forecast so that I can plan ahead.
• US-06 As a user, I want to switch between Celsius and Fahrenheit so that readings match my preference.
• US-07 As a user, I want clear retry behavior when a lookup fails so that I am not stuck.

The default visual language is a dark navy base (#080E21/#091125) with cyan accents, soft card edges, bright temperature text and weather-dependent sky effects. The core interface should remain usable in portrait phone orientation and accommodate smaller displays.

• Keep essential measurements visible before secondary details.
• Label icons with text, not color alone.
• Maintain sufficient contrast and touch-friendly controls.
• Provide feedback while searching, retrieving location and updating.
• Honor reduced-motion preferences where the platform supports it, without hiding data.

First launch with location permission

1. Open MyWeather and view the welcome/loading state.
2. Grant GPS permission when requested.
3. App retrieves coordinates and requests current and daily conditions.
4. Dashboard displays place, condition, highlights and three-day forecast.

Manual city search

1. Enter a city name in search.
2. App resolves a matching location through geocoding.
3. App requests forecast data for the resolved coordinates.
4. Dashboard refreshes and stores the selected city where supported.

• App launches without blocking exceptions on supported test devices.
• GPS permission accepted and denied flows are validated.
• City search with a valid and invalid query produces appropriate feedback.
• Forecast UI updates correctly for multiple weather conditions.
• Three-day highs/lows and sunrise/sunset reflect provider data.
• Unit toggle changes values, and saved unit persists on relaunch.
• Refresh control avoids duplicate/conflicting requests.
• App is tested on small and large Android phone screens.
• Production APK/AAB package, version and signing are checked.
• Play listing artwork, official screenshots, short/full copy, permissions and privacy disclosures are finalized.

Features not assumed to exist in the current source include user accounts, social sharing, radar maps, push alerts, widgets, historical analytics and server-side user profiles. Potential future work may include severe-weather alerts, more day ranges, offline caching and tablet-specific layouts, subject to product priority and API capabilities.