Ecosphere
  • Introduction
  • Elevator Pitch
  • Pitch Deck
  • Lean Model Canvas
  • OVERVIEW
    • Mission
    • Problem Statement
    • Ecosphere Prime Solution
    • Benefits
    • Value Proposition
    • Use Cases By Industry
    • Achieving Net Zero
    • Technology Platform
    • "Waze For Weather"
    • Strategic Roadmap
  • Technology
    • Climate Intelligence Network
    • Climate Nodes
      • Prototype
      • Device Mockup
      • Device Setup
      • Node Location Planning
      • Node Explorer
    • Smart Nodes On Hedera
      • Web3
      • Smart Nodes Vs Smart Contracts
    • DIDs and Verifiable Credentials
    • Peer-to Peer Data Sharing
      • How We Use Hedera
      • Hedera Topics
      • Data Tokenization
      • Data Sharing
    • Decentralized Identity
    • Micro Royalties
    • Fractional Ownership
    • Integration
      • Climate Data Workbench
      • API
    • AI Forecasting
  • Functional Flows
    • Registering A New User
    • Registering A New Node
    • Data Collection From Nodes
    • Data Tokenization
    • Data Sharing
    • AI and DLT
    • Marketplace
    • Fractional Ownership
  • Community Product
    • Product Community Fit
    • Product Vision
    • Minimum Viable Product App
    • Wireframe
      • Onboarding
      • Walkthrough Tutorials
      • Wallet Creation
      • Location List
      • Weather Information
      • Location Options and Support
      • Timelapses
      • Animations
      • Weather Station Setup
      • Search and Explore
      • Settings
      • Sharing and Notifications
    • Style Guide
    • Visual Design Elements
    • Usernames Feature
  • Commercial Product
    • Sector Focus
    • Product Market Fit
    • Comprehensive Reporting and Dashboards
    • Climate Data Oracle
    • Go-To-Market
    • Competition
  • Tokenomics
    • Revenue Drivers
    • $PRIME Token
    • Value Capture Mechanism
    • Reward Structure
    • Locale Coverage
    • Nodes For Public Good
  • Community
    • Whitepaper
    • Public Good
    • Joining Ecosphere
    • Governance
    • Awareness
    • Disaster Readiness
    • Early Warning System
    • Socials
  • Project Developer
    • About
    • Team
    • Funding
    • Testnet Accounts
Powered by GitBook
On this page
  1. Community Product
  2. Wireframe

Location List

Location List Functionality and Content: The location list screen displays a user's relevant locations in a primary location (first navigation tab) that not only addresses the previous problem of users' inability to locate their followed locations, but also reinforces the primary value of BloomSky—providing weather through followed locations or purchased BloomSky weather stations. It provides adding, editing, rearranging, and removing capabilities for users to customize their list. In addition, the screen allows the user to quickly scan weather information for their entire list including weather station status and location weather conditions. To address the label problems that previously confused users, we ensured that only relevant and significant information necessary to determine a location is provided on the list. Further information would be provided after tapping on a location. To address the information hierarchy problems, we ensured logical information grouping and visual division (see screens 1–2).

Editing a Purchased Weather Station: If a user decides to edit a purchased weather station, they can change the station's information including name, description, location, and search privacy. In addition, they can initiate station processes such repositioning the camera view, relocating a station or replacing a station while keeping continuation of data records, deactivating a station temporarily to e.g. change the wifi network, and linking a BloomSky indoor weather station if its placed at the same location. Information and functionality is ordered and grouped by frequency of change and relation to one another (see 3).

Renaming a Followed Station: Users can rename a nickname for a followed location (see 4). The nickname provides the option to use a more relevant and memorable name to the user (e.g. office, work, school) rather that using a default of address or weather station name designated by the owner.

Mental Anchors: To address the previous problems of navigational and informational confusion (i.e. "where am I" and "what am I looking at"), simple functionality such as renaming, removing & adding were designed as modals and locations being edited were referenced in order to create a strong association with where the user was in the app and what was being edited. (see 4–6).

PreviousWallet CreationNextWeather Information

Last updated 7 months ago