Generic outcome confirmation pattern
- Lite Farm
Most actions the user performs are initiated via a user interface on the front end. The front end then communicates some amount of data to the back end, where the back end performs some logic on that data and persists any changes in the database. The back end should also generate some sort of a response to the front end (and ultimately the user) to inform them of the outcome of their attempted actions. This response often consists of two parts:
Navigation to a particular page based on outcome
Toast showing the explicit outcome (and in the case of a failure, the option to try again)
More rarely, a response may contain a third part - something to the effect of would you like to repeat this action again? For example, when adding a crop to a field it is very likely a farmer will add many crops in a row. In this case, a templated next step that remembers the field is intuitive and saves the farmer time.
The following is a generic pattern for handling this very common pattern:
https://app.lucidchart.com/invitations/accept/1f38e14c-d223-4ae4-82c2-2b4635c12221
Use Cases:
Use Case | FE | BE | Responses |
|---|---|---|---|
Invite a new user to my farm | Enter name, email, role, wage, etc. and click “Invite” |
|
|
Add a new crop to my field | Enter type of crop, variety, percentage of field, price per lb, estimated yield, etc. and click “Save” |
|
|