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

Usernames Feature

PreviousVisual Design ElementsNextSector Focus

Last updated 7 months ago

Focus was placed on the aspects central to increasing user privacy and security. This included creating username functionality and creating station nicknaming functionality.

Feature Details: Usernames were created to protect the privacy of users because at that time, emails were used for display names to the public. Usernames were created to by unique per user.

Feature Flows: The usernames feature were account for three user flows: 1. New users opening the app after the update, 2. Existing users opening the app after the update, 3. Users changing their nickname after the first open from settings. New and existing users have the same flow for opening the app after the update, with one exception for existing users. They are presented with a modal notification letting them know why they will be required to create usernames and what they will see next, since existing users will have expectations of what they will see upon opening the app and their expectations will not be confirmed. Afterwards, the user will see a screen with a profile image populated if they had previously uploaded one or a blank profile image placeholder that states that this field is optional, alongside an autopopulated username based on their email address (without @domain.com) (see diagram 1). If they decide to change either fields, they will be directed into the photo and username flows as appropriate (see 2–3).

REDO