Skip to content

Latest commit

 

History

History
88 lines (64 loc) · 4.37 KB

File metadata and controls

88 lines (64 loc) · 4.37 KB

Pitch: Imagine a social platform that helps students transition from elementary school to middle school. Bubl is a school specific social network and friendship connection tool.

MVP: User can create an account, join an existing school account, and search for existing Bubls to join. They can explore interests through hashtag searches. They can connect with others and share experiences. Proposal Bubl helps make it easier for young students to transition to the next stage in their educational career. Students can create an account connected to their school, connect with other students in the same school, and join different groups based on different interests. By making these shared interests easier to discover and organize, Bubl helps ease students into creating new, deeper friendships so they can be more effective students sooner.


  • What problem does your app solve?
    • Students finding relevant and age appropriate content
    • Helps solve the problem of students experiencing all the different emotions they might have when transitioning from elementary to middle school.
  • Be as specific as possible; how does your app solve the problem?
    • Gives students relevant and age appropriate content and guidance
    • Gives parents the ability to monitor online content their kids use more effectively
    • Lets students connect with other students from their new school
  • What is the mission statement?
    • We want to encourage students to expand their social Bubls

Features Users can create their own accounts. Users can join groups, or “bubls” based on interests of any kind. These are basically user groups with a post wall.


  • What features are required for your minimum viable product?
    • Users can create personal accounts
    • Join an existing Bubl
    • Message board on each interest page (“Bubl”)
    • Users can search for Bubls by hashtag
  • What features may you wish to put in a future release?
    • Admin privileges to create a school
    • Real time messaging between 2 users
    • Class code to join a school
    • Users can follow each other or friend each other
  • What do the top 3 similar apps do for their users?
    • Imageboard sites allow comment threads
    • Ning allows people to make small social networks
    • Twitter allows users to search by hashtag Frameworks - Libraries

  • What 3rd party frameworks/libraries are you considering using?
    • LESS
    • Redux
    • React
  • Do APIs require you to contact its maintainer to gain access?
    • No, we’re building our own API
  • Are you required to pay to use the API?
    • No, we’re building our own API
  • Have you considered using Apple Frameworks? (MapKit, Healthkit, ARKit?)
    • N/A For Data Scientists

  • Describe the Established data source with at least rough data able to be provided on day 1.
  • You can gather information about the data set you’ll be working with from the project description. Be sure to collaborate with your PM, and your Backend Architect to chat about the resources you have.
  • Write a description for what the DS problem is (what uncertainty/prediction are we trying to do here? Sentiment analysis? Why is this a useful solution to a problem?)
  • A target (e.g. JSON format or such) for output that DS students can deliver to web/other students for them to ingest and use in the app

Target Audience


  • Who is your target audience? Be specific.
    • Elementary school students moving into middle school.
  • What feedback have you gotten from potential users?
  • Have you validated the problem and your solution with your target audience? How?

Research


  • Research thoroughly before writing a single line of code. Solidify the features of your app conceptually before implementation. Spend the weekend researching so you can hit the ground running on Monday. Prototype Key Feature(s)

  • This is the “bread and butter” of the app, this is what makes your app yours. Calculate how long it takes to implement these features and triple the time estimated. That way you’ll have plenty of time to finish. It is preferred to drop features and spend more time working on your MVP features if needed.
    • Message board with comments:
      • Frontend: 1 day (estimated 3 days)
      • Backend: 1 day (estimated 3 days)