Challenger Project

Software
Phase 1+2 RFP
Summary/Overview
Phase two of this project will produce an MVP web app to upload, view and
archive gps tracks in the .gpx and .csv file formats, as well as syncing
functionality using Garmin Health API to sync tracks from Garmin Connect and
Google Drive API to sync files from specified Google Drive folders. User login
functionality so that new users can create an account and save tracks to their
account. Basic private and public sharing features.

Developer will create three web pages to upload .gpx files to a database, to view
those tracks, and to view a list of uploaded files.

We look forward to receiving your proposal to work on this project.

Technical Stack
Preferred technical frameworks are as follows:
● Back End Framework: Django
● Front End Framework: Vue.js
● Database: Postgres
● Mapping Data Framework: Mapbox
● JS GIS Library: Openlayers
● Deploy code to Heroku
Scope Of Work
Phase 2 will produce a functional MVP which can be used to sign up new users
and begin to build the business operations.

● Deliverables: See Deliverables and Wireframe section of RFP.

● Hours of Work: About 100 hours of work to achieve an MVP.
● Deadline: Hoping to complete Phase 2 by end of January.
● Compensation: Payment will be on an hourly basis.
● Evaluation: Code to be uploaded to GitHub repository every 10 hours of
work. Completed code should be deployed on Heroku.
● Phase 3 and Future Work: Phase 2 work will be evaluated and Phase 3
work will be available once business operations get ramped up.
Deliverables
Phase 2 should be completed within one to two months. The following deliverables
should be deployed and functional on Heroku:

1. “Upload New Track” web page - with drag and drop upload functionality
2. “Track Index” web page - displaying a list of all uploads in database
3. “Track Details” web page - with zoomable, panable, playable map viewer
4. “User login” and “user registration” pages
5. Sharable viewers

Deliverables should have consistent styling, but will likely be restyled after we start
working with a designer.
Timeline
December 2019 January 2020 February 2020
Define scope of Interview/hire
work developer
Phase 1
Development
Evaluate Phase 1
Work
Phase 2: MVP Development
Implement MVP
Tweak MVP with Developer to improve usability

● Start date: Phase 1 development to begin NO LATER than January 1.

● MVP will be built and refined through February, then product will be
monetized and Phase 3 development will begin.
Comparison Projects
Phase 2 should deliver an MVP comparable to ChartedSails
Additional Requests
In your proposal, please provide an estimate of how you would break the work into
10 hour segments so that we can evaluate the work as we go.

I.e. What portion of the work do you expect to be complete after ~10 hours, and
how can we test that work before proceeding? 20 hours? 30 hours? etc.
Wire Frames
Link Garmin Connect Account

Link Google Drive Folder

Future Development: Phase 2 and Beyond
As functionality gets built out, the track viewer will eventually display graphs of
time-stamped variables associated with geographic position (for example, graph of
speed in pane 2 below). This is outside the scope of Phase 1 or 2. 1. 4.

In addition, if a segment of track gets

selected by a user in one pane, it
should also get selected in all other 3.
3.
panes (segment 3 as shown here).

A pane should be able to calculate and

display descriptive statistics of a 3.
selected segment (pane 4).
2.
Project Resources
Sailboat icon

Sample .gpx track