An Update on TopForty.it

Figured I would give a quick update as to how TopForty.it been doing. We’re about 2 weeks in, and the response has been great. People seem to love the idea, the execution and the UI/UX, which is heartwarming although I still think it’s rough around the edges (won’t tell you where because then you will notice it =D ).

Some stats: In 2 weeks, people have listened to over 5000 songs (5194 as of last night), totalling in a little under 25,000 minutes. Our visitor return rate is over 60% and the average time spent on site is around 30 minutes. These numbers seem to be increasing, which is good considering the fact that we haven’t really promoted it much (blogs, reddit, HN, etc.).The growth seems to be organic with 50% traffic from Facebook. As we add features, we plan to hit Hacker News and some blogs.

Update: Techvibes did cover us from the demo we gave at Velocity’s end-of-term Demo Day. Since them, we’ve also been featured on GigaOm and The Next Web

Update: Here are the photos from Velocity’s Demo Day.

It’s been really fun to work on this project. I think where we are at now is interesting as we are trying get it out of the “hack” stage and into the “software” stage. Up until a certain point, you don’t give much importance to architecture, focussing on getting features out as quickly as possible. This is changing as the LOC grows. Since all the application logic is in JS, I have to spend a few days really cleaning that out. The good news is that YUI does a lot of the work for you, so I won’t have to refactor too much. I will take that time to pull in some of the new Y.App stuff that’s in 3.5.0.

I really do wish to write a blog post at some stage detailing how the UI works – as much as for my own records as for other people’s understanding. I have exams going on now, so it’ll probably have to wait till mid-December. I have started, but don’t want to publish something that’s half-baked.

What building and releasing a web app in 3 days taught me

Recently, me and two of my friends launched adore.ly, a Facebook-enabled web app that allows you to “adore” someone, and your identity doesn’t get revealed unless they “adore” you back. As the app has been online for a few weeks now (2 weeks as of this entry), I have had a chance to reflect back and think about what I did, what went right and what went wrong. This post serves as a way to record my thoughts and to share my experience with other students trying to get something out there.

Lesson #1: Build fast

We built most of the app during the Facebook hackathon that was held at UW. 24 hours of coding and brainstorming later, we were able to present a crude version to the crowd. The next week was spent polishing the app and working more on the front-end. We basically had adore.ly up and running in under 7 days.

Lesson #2: Release, then fix

It was very easy to find flaws in our app and we were tempted to push the release date further and further back. However, just launching it was the best move we made. It made us fix bugs and iterate faster since we knew people were looking at the site.

A slight caveat: We launched Feb.7 and posted on Hacker News and Reddit (with good results) on Feb. 8. In hindsight, waiting till Feb.14 (Valentine’s Day) would have probably been smarter.

Lesson #3: It’s not just the code – it’s psyche

I think this is one area where we didn’t do as well as expected. We felt that these “anonymous” adores wouldn’t be “creepy” since they came from your friends on Facebook, and so you knew all of them. We were 60% right. Turns out that guys agreed with us, but some girls didn’t. As a result, these girls did not want to send out adores, or did not respond to adores that they were receiving.

The point I’m trying to make here is to understand the psychology of the user and whether your app will be in their comfort zone, as far as their thinking is concerned.

Lesson #4: Know how to reach your market

It’s one thing to have a market or target audience. That’s something every app should have – otherwise why are you making it? However, things get tricky when you don’t know how to reach your target audience. For example, the idea behind adore.ly could go viral in high-school or in more conservative countries (such as India), but we weren’t able to figure out exactly how to target those people. Most high-schoolers dont read Hacker News or TechCrunch or tech blogs in general. They are on Facebook and Twitter, but our friend lists didn’t have this age group. I think luck is important in succeeding here.

Lesson #5: Have a well-rounded small team

We did really well here. We had two coders, me and Victor, and Fei Jing was in charge of business and promotions Victor is a backend guru and coded up Python super-fast, while I worked on the entire front-end. Having specific roles for each person really helped, as we all knew exactly what to do. At the same time, we were small enough that we could take decisions really quickly.

UI Innovation in Twitter for iPad

Engadget just posted their review of Twitter for iPad (which btw, was released a few hours ago), and the video review really highlights some of the thought that the Twitter development team have put into the interface.

It also emphasizes my belief that no matter how great an app is, the average person (ie: non-techie) won’t appreciate it without an interface that complements it.

Anyway, check out the video below!