Challenge Summary
This challenge targetting Admin interactions scenarios, we've finished the farmer wireframes scenario (attached) which you can use as references.
Round 1
Initial submission for client reviewAdmin Screen
01. Dashboard Screen
02. Weather Forecast Screen
03. Tips Screen
Round 2
All requirements like stated in challenge details with client feedback appliedAdmin Screen
01. Dashboard Screen
02. Weather Forecast Screen
03. Tips Screen
04. Farmer User Screen
05. Help & Feedback Screen
Background Overview
In Guatemala, 5 million farmers lack access to location-specific weather information and thus suffer major losses to their crops. Information exists but is not conveyed in the right way and time. 500 million people worldwide are smallholder farmers. They are a great asset of global agricultural economy, producing 80 % of the food consumed worldwide. However, they are living in very difficult conditions, and out of them about 400 million are among the poorest and hungriest people on the globe (half of the world's hungry people).
In many cases, such as in Guatemala, not only smallholder farmers do not produce any surplus for selling, but barely manage to sustain their families and often work another part-time job to survive. Their crop production and their overall conditions could be drastically improved if they would have access to reliable, specific and updated information on weather and agriculture. Information about weather, for example, could help them take the right decisions and avoid heavy losses; actionable tips about agriculture could ensure they follow modern and effective techniques in agriculture, rather than relying only on traditional knowledge; information about prices could guarantee fair market conditions for their crops; nutritional advice could help them follow a more balanced diet preventing nutritional deficiencies.
Information about weather, agriculture, nutrition and market already exists, being produced by different stakeholders and sources in each country – national meteorological office, researchers, UN agencies, and NGOs. However, this information:
- Does not reach poor farmers
- Is not in a format that can be easily understood by them.
In the case of weather forecasts in Guatemala, for example, only a 30 % of farmers have access to generic sources of forecasts (radio or TV), far from being actionable or specific-enough for local microclimates.
Challenge Goals:
Create a user-friendly, low-bandwidth smartphone app / website providing location-specific information, including weather alerts, agricultural advice & nutrition tips
Focus Area:
Connectivity, Agriculture, Climate Services
Key Features:
Must Have Features
- System will pull weather automatically from AccuWeather.
- System allows administrator to send agricultural tips (what to sow & when), Ability for administrators to assign text-based agricultural tips based on a geographic area.
- System allows administrator to send nutritional tips
- Ability for the user to receive a weather forecast for the next 7 days.
- Ability for the user to receive text based agri-tips based on geolocation
- Ability for the user to view information about prices.
- Ability for the user to receive text-based nutritional tips
- System allows administrators to send price alerts
Nice-to-Have Features
- System allows feedback from farmers to administrators
- System allows users to send question and to answer each other questions
Future Features:
- Spoken Languages, What spoken language or languages is this solution based on? (For example, English, Mandarin, Hindi). For the launch in Guatemala and LatAM the solution will be developed in Spanish
User Case Scenarios:
Farmers
- As a farmer, I want to view weather predictions for the next 5 days in my village ("Risk of heavy rain in the next week")
- As a farmer, I want to view seasonal forecasts ("average of 25 degree for the next 3 months")
- As a farmer, I want to receive tips on what to sow and when ("Consider sowing 'maicillo' rather than maize, you have more chances to have a good production")
- As a farmer, I want to ask questions to fellow farmers or experts ("What kind of fertilizer can I use for my tomato plantation?" or "My plants have a white fungus. What can I do?")
- As a farmer, I want to answer questions from other farmers
- As a farmer, I want to receive market prices for the main crop I grow (e.g., beans, corn, potato, vegetables)
Administrators
- As an administrator, weather and forecasts will be automatically pulled from AccuWeather.
- As an administrator, Agricultural tips will be manually pulled/ added
- As an administrator, I want to be able to send weather alerts to farmers in case of a sudden change
- As an administrator, I want to be able to track how many farmers have the application
- As an administrator, I want to be able to receive feedback from farmers and respond
Screen Flows (Admin)
The following screens only for recommendations, if you have a better concepts that will provide better solution for our goals, please feel free to create it.
Admin Screenflow Suggestions
01. Dashboard Screen
- Default page that appear when admin open the apps.
- Show list of application activity (discussion, feedback, things to do, weather and tips data, etc)
02. Weather Forecast Screen
- Weather and Forecasts will be automatically pulled from AccuWeather
- Weather forecast information needs to be divided based on the farmer location.
- Ability to view and import data from external source regarding weather information (satellite data, weather agency, etc)
- Ability to override and send sudden changes/alert regarding weather information to farmer (if any unusual weather condition appear)
03. Tips Screen
- Admin will be able to send text based information/tips regarding agriculture or nutritional tips to farmers from this screen (2 category).
- Admin will needs to set the information/tips content based on farmer location.
- Check "sampleTips.txt" for sample tips content.
04. Farmer User Screen
- Admin will be able to see all farmers that use the application (how many farmers download the apps)
- Admin will be able to filter farmer information based on the location/how long use the apps/active condition, etc?
- Admin will be able to see farmer details information
- Admin will be able to track farmer farming/agriculture improvements based on time/location/etc.
- Admin will be able to add farmers to group based on location.
05. Help & Feedback Screen
- Admin will be able to see any feedback from farmer (complaints/information request/etc) and set the feedback progress status.
Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn
Design Requirements:
This web app will be responsive and design elements should be easily translate to working on different device sizes. Please provide all screens in desktop (primary goal) and mobile version (nice to have/if you have a time).
Desktop: 1024px width with height adjusting accordingly
Documentation:
- sampleTips.txt
- farmer-wf.zip
Target Audience:
- End users: Smallholder farmers
- Additional users: Administrator to manage users & feed it climate information
Judging Criteria:
- Overall User Experience
- Completeness and accuracy of the wireframe as defined in the challenge spec
- How well your wireframes provide a consistent user flow.
- How well your wireframe captures all the functionality.
- Any suggestions, interactions and user flows you recommend (provide any notes or comments for the client).
Submission & Source Files:
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
All requested contest requirements as clickable HTML files generated by Axure. All the content must be listed and the pages are linked together to show page flow.
Source Files
Wireframes should be built in Axure. The resulting source files used to generate the clickable HTML files.
- All the content must be listed and the pages are linked together to show page flow.
- All fully editable original source files of the submitted wireframe as required by the contest under "Source Files" in the sidebar should be included in your Source zip file.
Final Fixes:
As part of the final fixes phase, you may be asked to modify content or user click paths.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.