review my startup, a planning/analysis app for cyclists
buro9: Nice.Questions I have:
1) Is your home location or post code displayed to anyone else? If so could you by default "approximate" the location to others unless a user specifies that they want their precise home location shown. Reason: Bike theft. Don't tell someone precisely where your bikes are, especially when combined with data showing when you're likely not going to be there.2) Upload photos of equipment/accessories. Add a Flickr picker... I immediately balked at having to go to Flickr, download a photo just to re-upload... actually a URL in addition to a browse would sort this out pretty simply.3) I'm pretty sure I said to hide my email address, yet options implies it's visible.4) Time-zone... set it according to home location.5) Health page... weight inc' bicycle and gear? Nope, you should put the weight of equipment on the equipment page... this data varies depending on what bicycle I take out.6) Health page... age instead of date of birth?7) Route drawing... remember prior preferences. Avid cyclists will start to begrudge always telling the tool that they aren't "Driving".8) Full screen mode is nice, as is the elevation cross-section. A few of the route segments seemed to be wrong but I suspect this is Google's doing and not yours (it would send me needlessly down side-streets and correcting it is a pain in the ass).9) Route planning should allow for the addition of markers. Think of things like: Lunch stop, viewpoint, toilet break, etc.10) Consider a way of displaying several routes on the same page... think of scenarios like the Dragon Ride and the short and long rides sharing a considerable chunk of the route (show specific routes on the same page). Also consider scenarios like "I'm going to ride Ventoux, allow me to visually compare the routes in that area" (show routes that meet a search criteria on the same page).11) Haven't yet used the GPS functionality, but you appear to have the basics covered.12) I liked the embedding widget... but it's ugly. Does it have to be in black? Could you not have a prettier logo?13) Before I enter in too much data I'd like to see when it's no longer free. Even if everything is free now, you should let people know at what point it ceases to be free. The issue is... "Why should I invest my time and data with you when I don't know how long the functionality offered will be offered to me at the price you're giving it to me (currently free)?". Even if you just say, we're not sure, but in this ballpark when we feel that we have a finished product... you'd increase the amount of trust and faith I have in supplying you with so much data.14) Route sharing, route widgets... go beyond the simple. Look at this scenario: http://www.londonfgss.com/thread31699.html A single ride, with over 100 participants, that recurs and changes direction... yet it's obvious it should only be stored as one route, but you should allow multiple people to say that they're riding a route in the future (scheduled event rides as well as individual rides in addition to route planning). There's a big space for being the people who can route plan sponsored rides let alone community rides and things like that.15) I'd consider adding ride photos or something to pull in photos from Google and show those. If someone is remotely route-planning (prior to a foreign vacation) they will want to know whether the place looks good... i.e. This: http://ridewithgps.com/routes/23644 does not communicate the beauty of this: http://images.google.co.uk/images?q=nesque%20gorgesOverall it works really well with even the poorly mapped areas: http://ridewithgps.com/routes/23644I run a large bike forum and will pimp it there and ask for more feedback for you: http://www.londonfgss.com/thread35392.html