Skip to content

asb43/pollinator-pathway-android

 
 

Repository files navigation

Pollinator Pathway

MoBAS Course Project

App name

App description as it would be listed in the Google Play Store

How to use template: replace all italicized text with described content

Customers

Personas

  • Matt has a farm and just joined the Pollinator Pathway.
  • Amy’s a member of the PNW Pollinator Pathway and her pollinator garden has expanded.
  • Alex is the president of the PNW Pollinator Pathway.

Pain points and user needs

  • Description of pain point or user need the app aims to address
  • Matt is unsure how to register his site with the pathway.
  • Amy is having difficulty updating her information for her site.
  • Alex does not currently have administrative access and control of accounts

Scenarios

  • Solution agnostic descriptions on how the app meets the personas needs
  • Matt has a farm and just joined the pollinator pathway. He wants to set up his site information with a name, description, photos, and a link to his website.
  • Amy’s Pollinator garden has expanded and she can go on the app to edit her information.
  • Alex wants to have administrative access and control of accounts.

Competitive analysis

Strength, weaknesses, opportunities, threats Summary of top competitive apps

Implementation

User stories

Prioritized list of functional components that describe the implementation from an end-user perspective.

  • P0: User [action] description
  • P(0): Farmer Anna has just received her boxes in the mail and wants to set them up. She sets the box with its QR code in its location, then scans the QR code to register the box with the Pollinator Pathway server to add the box to the pathways map.
  • P(0): Alex wants to have administrative access to approve new accounts and photos before they are published on the site. She logs into the app and approves and denies new content and edits. P(0)
  • P(1): Liesl is a member of the Pollinator Pathway and wants to see other sites on the PNW Pollinator Pathway and view their information. She uses the app to view other locations on the map and view their profiles.
  • P2: Bradley is walking by a site on the PNW Pollinator Pathway and wants to see the site information. He opens the app on his phone, scans the QR code, and views the site's profile and information page.

Walk through

Screens

Images of key screens covering all the user stories

Color

  • Primary color: hex color
  • Secondary color: hex color
  • Primary text color: hex color
  • Secondary text color: hex color

App icon

Logo - Spash Screen:

Icon - Google Play Store:

Integration

What external APIs or services do you have a dependency on? Google Maps, authentication providers, REST APIs?

Future considerations

Usability summary

Key learnings and takeaways that were applied from the last round of usability studies on the high fidelity prototype. Call out anything that hasn't been addressed in the design or app components to continue investigating in the future

Monetization

Financial options for ongoing support and development

Measuring engagement

Define active usage for your app, the actions over a day and month that indicates someone is a user of your app.

Stretch features

Future experience considerations not yet explored and tested

About

MoBAS Course Project

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • Java 100.0%