Makes sense. The idea of using Handlebars instead of embedded Javascript is that the template can't actually change the model, just get data from it, so there's no real logic on the template. Of course this is all theory, as I said in the blog post, it was just an idea. Once I use this approach, I can definitely state the pros and cons.
Yeah I've been thinking about what I can do with this, but a location based chat has been done before. I was thinking of keeping it simple. A mobile version maybe, I use CSS3 Media Queries to show different "versions" of the app on different devices but I was thinking of doing dedicated mobile app... When I find the time of course lol
Well, there's a lot of factors here... HTML5 Geolocation is not very accurate if the device doesn't have a GPS. You can always enter your location manually from tne settings pane (the more specific you are the better). If the app got stuck at "looking for data around you" then one of the services (twitter, instagram, foursquare or youtube) failed and the app tries to get results from the services again. Sorry if your expirience wasn't good :(
Am using the APIs from twitter, instagram, foursquare and youtube to get the data. Google maps api to display the map, user locations, directions, etc. and the yahoo placefinder api for geocoding and reverse-geocoding. Everything is done client side with jquery, backbone.js and handlebars.js
EDIT: You don't need an account from none of these services. rround just uses your location and the rest is magic ;)
I forgot to mention that it also uses local storage to show you the people that were rround you on your last visit.
Yes, the geolocation API can act weird sometimes :( try to clear you cache or try a different browser. You can alway enter your location manually (not the same but it's something). I'm sorry if the app didn't worked for you :(
Great answer!