Hydrosphere - Cloud platform to analyse water quality



















Hydrosphere, a cloud-based application, specializes in water quality analysis, offering customizable site configurations and effective monitoring tools. The project involves restructuring legacy water quality analysis applications to enhance competitiveness, requiring careful planning and user-centric design to ensure success and market relevance.

Product info

Hydrosphere is an application hosted in the cloud, focusing on water quality analysis. Users have the ability to establish sites and customize their data configurations. It provides a range of functionalities to aid in effective and efficient site monitoring and management. Initially, the product launch focused on integrating key Xylem devices, with plans to incorporate third-party devices in subsequent phases. The product has an extensive roadmap, introducing new data models and advanced analytical capabilities.

Role

UX Designer

User research, Competitor analysis, Information architecture, Wireframe,  Interaction design,  Prototyping and testing, Visual design

Project info

The project involves restructuring and redesigning outdated water quality analysis applications, such as Storm Central Waterlog, Aanderaa Geoview, and Tideland, to gain a competitive edge, with phased implementation to ensure success.


The project commenced by consolidating various water quality analysis applications operational until 2018. These legacy applications required restructuring and redesigning due to their outdated nature and inability to provide a competitive edge in the market. Examples of these legacy applications include Storm Central Waterlog, Aanderaa Geoview, and Tideland. As a UX designer, tackling this project presented a significant challenge, particularly because it was my first experience in water quality analysis. The project is being implemented in several phases to ensure its successful execution.


Direct observation

To craft a pleasing user experience, it's essential to grasp their natural work environment, aiding in deeper understanding, marking my initial step in requirement assessment. 


Surveys & User interview

User interviews were conducted with various roles: 

  • Application admin: overseeing all accounts and customers
  • Customer admin: creating sites
  • Scientists and Technicians: monitoring sites 
  • Data reviewers: handling reports for organizations.

Interviews took place in users' natural work environments to enhance comfort and confidence. Questionnaires were meticulously prepared, with each user interview lasting approximately half a day.




Valuable insights were gathered from the interviews, informing the creation of a user-centric experience.


Competitor analysis

Eagle.io stands as our primary competitor, boasting a significant market share and an array of commendable features. However, our distinctive edge lies in providing sensors to the market, a capability Eagle.io lacks. Leveraging these sensors and data loggers, Hydrosphere offers a unique Databack fill option, regarded as advantageous by users.



Solution design

The design of Hydrosphere prioritizes scalability as a core aspect, with plans to incorporate third-party devices and advanced analytical features in its roadmap. Users should transition seamlessly with minimal learning curve from legacy applications used for over 15 years.

Information architecture

Developing a robust information architecture was crucial for this project and product, particularly since it involved consolidating various legacy applications. One of the key challenges was integrating information from different applications and presenting it in a user-friendly manner.



Wireframe








Visual designs



Design validation

After finalizing the prototypes, I invited the users I initially interviewed for a design validation test. Given the scale of the application, it was crucial to avoid any frustrated users during usability testing. We established a simple usability lab with a PC and camera in one of our facilities. Users gradually responded positively to the application, finding it reminiscent of their legacy application, and quickly adapted to its functionality.

Key take aways

Merging multiple applications with different user sets poses significant challenges, as users tend to compare it to their familiar applications, raising concerns at any deviation observed
  • Future-oriented planning is essential for minimizing technical debt.
  • Strong foundational architecture is crucial for scalability when expanding the application.
  • Ensure the design remains relevant and competitive in the market.
  • Aim for a user experience that surpasses competitors' offerings to capture a substantial market share.