Dev environment photos do not include all of the renditions which can lead to errors when attempting to delete them.

• Lot of whitespace on the page, regardless of results
• Show more information about the hikes that are returned
• Searching for a common word, like "the" or "peak" is given the same weight as a word like Kilimanjaro
• Perhaps slightly too forgiving on results that match

using stellar.js [by Mark Dalgleish github.com/markdalgleish/stellar.js] on the about page will give the page that 'zing'

1. Vist a page with flickr photos, e.g. http://hike.io/hikes/mount-etna
2. Click on flickr photo (e.g. landscape)

Results: No flickr annotations.

Getting the error: http://api.flickr.com/services/rest/?method=flickr.photos.getInfo&api_key=d…f009f20c36657c94263e52674&photo_id=5992716730&format=json&nojsoncallback=1 403 (Forbidden)

This is somewhat hard to reproduce, and probably a result of firefox inserting random
into the contenteditable div.

Include email, twitter, anonymous feedback form.

1. Visit http://hike.io/#!

If a user already has a GPX file, there's no need for them to enter all extra data (location, max elevation, etc.) since it's all embedded in the GPX.

Upgrading to AngularJS 1.3 broke the unit tests. Fix that.

Ideally GPX versions of the routes would be displayed on the map, and it would be available to download / upload.

Currently hikes show up on the /discover page even if they are ready for primetime. Should filter based the new is_featured flag.

1. Add a new hike.
2. Search for it.

Results: Doesn't find the hike until the review process is complete (which can sometimes take hours depending on moderation speed)
Expected result: It would still show up in the search results even if it wasn't reviewed.

This is partially mitigated by the fact that currently all edits will go through the review process, so reviewers can manage conflicts.

1. Create a new hike with 0 elevation gain

Result: Facts summary box shows Elevation gain: ft
Expected result: Elevation gain: 0 ft

Things to add to the FAQ:

• Types of photos to upload (license, without watermarks, etc)
• How to edit, maybe a video of how it's done
• Writing good descriptions (an abridged version of something like: http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style)
• Reporting issues

For descriptions that go beyond the facts box, truncate them but allow the user to fully expand to the full description if they want to.

For example, searching for "Washington" should bring up the map with Washington on it.

Currently investigating geocoding options:

• Nominatim - Does not support fuzzy search for misspellings
• cloudmade - Incomplete data (e.g. searching for Washington doesn't bring up the state, but does bring up a couple of cities).
• MapBox - Works pretty well for coarse queries but for fine grain searches, like smaller towns and natural features (e,g, Yosemite) don't work. Also, hard to tell if fuzzy search works, but in demo it doesn't.
• geocod.io - Needs a very specific address in order provide relevant results, e.g. Washington return anything. Also no international support.
• Google Maps - Works pretty well, but there are some issues. Searching for Washington, from Washington state brings up DC.
• Google Places - Would require two API calls in order to get a location, but works pretty well. Would require a "Powered by Google" logo.
• smartystreets - Doesn't handle search by state. No international support.
• GovMapper - Seems to be US only and demoes don't work.

GPX data should already contain elevation data. A couple of questions still remain:

• How to cleanly represent this data
• How to handle out and back hikes?

1. Create a new hike with non-ASCII characters, such as Kaş - Limanağzı - Çerçiler

Resulting url: http://hike.io/hikes/ka-limanaz-eriler
Expected url: ASCII-cized version of url or escaped

https://devcenter.heroku.com/articles/ssl-endpoint

http://docs.angularjs.org/api/ng.$http

Google is going to be using this as a SEO signal, so it's important to fix.

Google "hike.io" on a mobile device and click the homepage, it redirects to a url with a # in it, that Angular does not handle well.

Use the Annapurna Circuit as example of a multi-trail hike that needs to be supported.

This is a known issue with Angular: angular/angular.js#1417

Common words like "the", "mt.", "trail", should be deemphasized for their effect on search.

The page is too start, especially for new users. Lots of good feedback on: https://news.ycombinator.com/item?id=7087927

Also consider moving discover content onto the homepage.

Seems to be related to: http://stackoverflow.com/questions/5557776/websockets-over-a-3g-connection

Could instead just request all the hikes at the beginning. Or do it all over AJAX.

Any time the frontend makes a call to the backend is an opportunity to fail, currently only logging the problems, not showing any useful UI.

Currently hike.io only supports imperial units. Allow user to change to the metric system. Should be easy with AngularJS's filters, the backend is already in metric.