Without creating an account, a user can search the database of missing bikes for information like a bicycle's unique serial number, brand, model, color, size, or the zip code from which it went missing. If your bike has gone missing, create a free account and fill in your bike's information. Searching Craigslist for a used bike to purchase? Check our missing registry to ensure you're not buying someone else's stolen property.
- Ruby
- Rails
- Cloudinary
- Sass
- jQuery
- SVG
- Lettering.js
- CoffeeScript
- PostgreSQL (via Interactive Ruby Shell)
- Active Record
- Bootstrap
- Font Awesome Icons
- Material UI library and framework
- As a bike purchaser, I want to be able to check to see if the bike I'm about to purchase on Craigslist is stolen property
- As a bike owner, I want to proactively add my bike to a registry so I can recover it quickly if stolen.
- As a law enforcement officer, I want to reference a missing bike index to return a recently recovered bicycle.
- As a bike owner whose bicycle recently stolen, I want to post my bike on a public forum to increase visibility and possibility of recovery.
- As a person who recently found an abandoned bike, I want to know if this is a missing bike and how to return it.
In order to save space on github, we have put all our wireframes into an Imgur album. Please copy and paste this link into your browser to see them.
We decided early-on to build an app that had a unique niche of dedicated users. Most importantly, we focused on creating a service that we would use and was relevant. Seattle is a bike-centric city, which unfortunately also makes it a target for bicycles thieves. After reading about Bike Batman, the Seattle vigilante who scours Craigslist ads for stolen bikes being flipped for a quick buck, we settled on a registry that could help the recover and prevent bike-related crimes.
Whiteboarding wireframes/ERD diagrams and clearly outlining our CRUD functionality kept the project organized and merge conflicts minimal, as everyone had a clearly delegated job. We separated components into self-contained partials which allowed group members to tackle features displayed on the same page.
Keeping organized with a clear vision of our minimum viable product allowed us to quickly and efficiently dial in our required features and move on to the fun stuff. We had time to try our hands at Cloudinary image uploads, interactive jQuery forms Nokogiri data scraping, SVG/CSS animations, and a hand-coded search function.