MVP & Schema Review

[vawhitehouse]

MVP

• [x] Production README should be your 7th MVP
• [x] You need CRUD functionality on at least one MVP - maybe routes and/or drills?

Schema

• [ ] Is profile_picture so users can upload their own image? If so, you won't need a column for this. We'll use Amazon Web Services for user uploads.
• Is there a reason you went with a decimal data type for lat/long rather than float? There are pros and cons for each option - let's talk about this when we meet.
• Let's also talk about segments/navigate - You may want to start with runs having a single start/end, then have segments as a bonus to work on later.
• comments: primary_key column should just be id

[lxg073000]

• Sorry for the shifting verbiage in my schema/mvps. Here's the translation:
  • Creating ~Routes~ (Supply Routes)
  • Saving ~Workouts~ (Buggout Drills)
  • ~Workout~ Feed (Scarab Feed)
  • ~Workout Stats/Totals~ (Buggout Drill Analytics)
  • ~Friends/Following~ (Trustees / Colony)

MVP

• [x] Added the Production README
• [x] Supply Routes are updated to include full CRUD cycle
• [ ] I'm not sure about the Buggout Drills update cycle.
  • Logic for analytics will live in the segments and be calculated from the waypoints' update_at values.
  • How the update_at values are triggered to refresh is not yet determined...
    • Updates could trigger dynamically from matching a user's current GPS to a waypoint. Or static updates could trigger from the User interacting with a button.

Schema

• [x] Removed profile_picture
• [x] Updated primary_key to be id
• Decimal data type for coordinates was just based off a shallow search on stackoverflow. I believe one of the recommended GPS library requires type decimal? I'll look into it before our next meeting
• Supply Route/Waypoint/Segment logic is meant to account for Dynamic and Static Supply Routes.
  • A Supply Route is initialized with a start-point with. The initializing the Supply Route also initializes a segment with a startpoint and endpoint of the same waypoint.
  • (Static) A User adds waypoints manually (via a map UI or coordinate pairs). This triggers logic to update the Supply Route's segments
  • The initial segment's end-point becomes be the newly added waypoint. And a new segment is created where the startpoint is the newly added waypoint, and the endpoint is the Supply Route's start-point.
  • (Dynamic) The User's Supply Route begins with their GPS provided start-point, but there would be no way to know what the next point would be. So the workaround is this initial segment of where the start/end point of the same value. Then their GPS updates the next waypoint and triggers the segment changes.