11 days ago I posted the launch notice for Triply. The only other place where I publicized it was on the Foursquare Apps list here. It was very surprising for me that given no “advertisement”, no web design and very little features it managed for 11 days to score:
- 103 user accounts – 83 Foursquare and 22 Facebook
- 2226 actions performed around the site
- 651 visits
- 432 visitors
- 10 Twitter followers
- 14 Facebook page fans
- 2 Feature requests in UserVoice (completed)
I used real time analytics (Woopra) to monitor the users navigation flow (not that there are many pages to navigate around) and that helped me to optimize the experience, especially in terms of login flow. For example instead of asking the user to sign in with Foursquare or Facebook to share a trip I redesigned it to show the actual page and only prompt for login when the user needs to import Checkins. As they say a picture is worth a thousand words, but the actual thing is priceless.
Other new features since launch are:
- Facebook Places Checkins support
- Browse trips interface where a user can browser trips, days out and experiences by City, Country and latest
- Allow trips to be downloaded as a .GPX file which users can open with Google Earth and Garmin sat navs. Adding support for other geo formats for other satnavs won’t be hard either.
- A lot of polish and fixes in the backend. Thanks god for ELMAH, which helped me log all problems around the site.
I am on a cross road at the moment as I need:
- A web design (well overdue)
- Someone to bounce ideas off and vice-versa (co-founder?) in which direction to take Triply as I think there are many directions Triply can go. For example I can make it the bit.ly for sharing trips/days out, etc or I can make it a trip diary type of thing by pulling and displaying photos of the trip from Flickr (using EXIF location data and search), etc. All fun ideas.
But how do both of those fit together? Doesn’t the design depend on the future features and vice-versa?