End-user experience
Plan, care, and continue.
01Read local weather information
02Create watering and fertilizing reminders
03Follow step-by-step planting guidance
04Review planting progress and history
05Access products, articles, and support
00Project overview
Not another plant-information app. A system for completing the routine.
Agriplant combines a mobile experience for planting activities with a desktop workspace that lets administrators maintain the content and operational data behind those activities.
Challenge
Make planting easier for users who need guidance, reminders, and visible progress.
Goal
Upgrade the early concept into a coherent high-fidelity mobile and desktop ecosystem.
Responsibility
Research, synthesis, user flows, information architecture, interface design, prototyping, and usability evaluation.
Method
Design Thinking: Emphatize, Define, Ideate, Prototype, and Test.
How might we make plant care feel like a guided rhythm instead of a collection of separate tasks?
Admin experience
Maintain the system behind the journey.
01Manage weather and plant-care information
02Create and edit planting guidance
03Monitor growth records and user activity
04Manage local agricultural products
05Identify usability and efficiency barriers
01Emphatize
Observe the routine before designing the interface.
Online observation, interviews, and persona development were used to understand the needs, habits, motivations, pain points, and expectations surrounding everyday plant care.
Remember the routine
Users need clear watering and fertilizing reminders so plant care does not depend on memory alone.
Understand the timing
Local weather information helps users decide when planting and care activities should happen.
Follow the process
Step-by-step guidance reduces uncertainty for users who are still learning how to plant.
See the progress
A planting history makes growth visible and helps users continue an activity they started earlier.
02Define + Ideate
Turn scattered findings into a product spine.
The research was grouped into recurring problems and translated into a feature direction for both the end-user application and the admin website.
Product question
How can one ecosystem guide both plant care and its supporting operations?
Active problem root · Memory
Plant care is easy to forget.
Reminders need to be visible, editable, and connected to a specific plant and care activity.
Synthesis evidence
Feature direction
Prioritisation becomes easier to scan when it reads like a sequence, not four screenshots.
The lanes below summarise the documented feature scope. The original prioritisation matrices remain available in the process archive.
01
Core journey
Must feel effortless in the first usable version.
Local weatherPlant-care remindersGuided plantingPlanting history
02
Support layer
Extends the journey after the core tasks are clear.
Agricultural productsCustomer-service chatbotArticles
03
Admin foundation
Keeps mobile content and operations maintainable.
Plant content managementReminder managementProgress monitoringProduct management
Information architecture
Two interfaces, one connected content model.
The mobile architecture focuses on completing plant-care journeys. The desktop architecture focuses on maintaining the information and records those journeys depend on.
03Prototype
Every final feature is visible without turning the page into a screenshot wall.
The complete mobile-user and desktop-admin high-fidelity scope now has its own interface atlas. Supporting process artefacts remain condensed below.
Final interface atlas · 11 documented features
Explore the final design in a tighter, cleaner layout.
Pick a platform, then move feature by feature. Everything stays visible without wasting space.
Mobile user experience
Authentication
01 / 07
Journey structure
Map the task before styling the screen.
The core mobile and admin journeys were translated into task flows so every screen had a clear purpose and a predictable next action.
Representative end-user and admin task flows
04Usability testing
The strongest story is not that the prototype looked finished. It is that users could finish the tasks.
Mobile and desktop testing used severity ratings and the Single Ease Question (SEQ) to identify usability barriers, task difficulty, and opportunities for refinement.
Plant-care user
Mobile application
Twelve tasks had no usability issue; one image-upload task revealed a minor limitation.
13 scored tasks
Coverage
7.00 / 7
Average SEQ
3.92 / 4
Average severity
SEQ 7 · Very easy13/13
Severity 4 · No issue12/13
Severity 3 · Minor issue1/13
Design response
Minor friction became a concrete revision list.
No critical or major usability problem was recorded. The useful work was therefore not a visual redesign, but focused clarification of control, feedback, and error prevention.
Open testing documentationAdmin reminder tasks
Time input required manual effort and caused hesitation.
Add a clear current-time option, improve time-entry affordance, and keep the field editable during reminder updates.
Plant and product management
Some dropdown and accordion patterns were not immediately clear.
Strengthen labels, helper text, selected states, and disclosure cues so controls explain themselves before interaction.
Admin progress-image management
A destructive image action was easy to trigger accidentally.
Separate the delete target from the content card and use a focused confirmation step with a safe cancel path.
Mobile image upload and admin product editing
Users needed clearer feedback after uploads and edits.
Support replace/remove states for selected images and add visible success feedback after an update is saved.
05 · Reflection
A case study should show decisions growing—not screenshots accumulating.
Agriplant taught me how research, structure, interface design, and testing connect across a mobile product and an operational desktop system. The final presentation now follows that same logic: evidence appears only when it supports a decision, while interaction keeps the reader moving through the story.