PLANTNET UI/UX REDESIGN
A plant discovery redesign—and a lesson in asking questions earlier.
Tap an image to open it, browse and zoom into the details.
Research should guide the screens
The design decision
This empathy map records a view of users’ needs. I made the polished screens first, so this work did not guide the initial design.
A persona is a working model
The design decision
Aarav is one proposed audience represented in the project. A persona alone does not validate a design decision.
Consider another perspective
The design decision
Rakesh represents another proposed audience with potentially different information needs.
Connect the screens
The design decision
The architecture board maps how the experience is organised beyond individual screens.
The lesson behind the deliverable
The design decision
This board brings the prototype and research material together. Finishing the screens was not the same as validating the experience.
What I’d do differently.
I would define the research questions, speak with users and test the direction before polishing the interface. Completing a redesign does not prove that it solves the right problem.
From a plant photo to a considered choice.
This iteration follows the identification task across mobile and desktop: choosing a photo, reviewing possible matches, comparing alternatives and saving an observation.
What changed
The revised flow separates a suggested species from a verified identification. An observation can also be saved as unidentified. Camera and connection recovery screens offer a next step, while confirmation screens keep the identification status visible. Paired light and dark screens now connect through Appearance settings, using the original mobile design’s Manrope typography, green palette and icons.
What the review found
Checking the prototype destinations revealed that saving an unidentified plant led into the suggested-species route. Separate save and confirmation states now retain the unidentified status. The mobile Identify and Saved destinations are connected. The comparison screen still needs an equivalent detail route for the second candidate.
The revised screens
Scope of the review
This is a screen and prototype review. The photos and matches are examples; identification, camera access and persistent storage are not implemented. Participant interviews, survey responses and usability-test results are not available for this revision.
Introduce plant discovery
What I set out to address
The home page sets the redesign’s visual direction and organises the entry points into plant content.
The thinking behind it
The challenge was to redesign the PlantNet application with a cleaner, more modern, and user-friendly interface.
A learning project: I designed the high-fidelity screens before research and testing. These are design intentions, not validated improvements.
Group related content
The design decision
The dashboard brings the website’s content sections into one view. Grouping was intended to make browsing more organised.
Give the collection a home
The design decision
The plant library gives collection browsing a dedicated destination.
Learning has its own place
The design decision
A separate learning page gives educational content a distinct place in the navigation.
Keep help findable
The design decision
The contact page supports the main discovery experience with a place for enquiries.
Start with the main journey
The design decision
The mobile home explores clearer grouping and a consistent green visual system on a smaller screen.
The photo comes first
The design decision
Photo selection is a distinct step in the identification flow, making the required input explicit.
Explain the result
The design decision
Identification results connect the submitted photo with plant information.
Beyond the plant’s name
The design decision
The detail screen expands the initial result into a fuller information view.
Keep discoveries close
The design decision
Saved plants give returning visitors a way back to previous discoveries.
Explore a social space
The design decision
Community is shown separately from the core identification screens.
Another way to discover
The design decision
Explore categories offer an alternative to identifying a specific photo.
A reason to explore
The design decision
Plant of the day is an editorial discovery concept for visitors without a specific search in mind.
Explore guided help
The design decision
The assistant is a conversational guidance concept within the plant experience.
A home for account tasks
The design decision
Profile separates account-related actions from plant discovery.