308 karma · joined August 21, 2009
The way I've tackled it before is let them do X first (select their celebs lets say) without registering. Drop the cookie and create a user record linked to it. Then tell them that if they register they can access their list from any computer (work and home are big sellers). It's pretty effective for getting registrations and you shouldn't encounter as many problems as you think you will. If you're encountering a lot of trouble getting users to register, give it a try for a couple of weeks and see if you get more adoption.
Alternatively you could let them pick their celebs first, then make them register. It's kind of annoying for the user but let's them see what's available (and get a little invested) before registration.
Anyway, just my 2c.
Having said that, why make people register to select their celebrities? If there's not a good reason then drop an id as a cookie and track their choices that way. I was not going to register, but had I been able to select the celebs right from the get go I probably would have done that then returned.
As for the idea - great! I already found a few points of interest and that's just from scanning the front page.
This way you never need to give glunote access and you can still use the system.
The reason we need access is that if you access glunote through the website we need to set your account to follow glu so that we can direct message you your search results. Thanks for the feedback and we'll change the language so this is clearer.
The premise is pretty simple, just follow a user "glu" on Twitter then to take notes send a direct message to glu. The system then stores the note permanently, i.e, "d glu dicount socks 1-800-555-SOCK". You can then search notes by sending a direct message to glu with a ? as the first character. For example "d glu ? discount socks" would return all your notes that matched "discount socks" as direct messages (actually at the moment it returns the best match and a link to all other matches).
It was originally just for me but I've opened it up to anyone. I'd love to get some feedback on what people think, where there might be improvements, what's missing, that kind of thing. Any feedback is greatly appreciated.
2. Not asking for help soon enough
3. Thinking that the market was broken but really just failing to understand the market
4. Never being "finished" enough to go live
5. Listening to experts
6. Completely and utterly underestimating how hard it would be to get customers.
You're completely right, it's a hard nut to crack, and gaining traction will be tricky, which is why I'd probably just start in a few major cities first, or maybe just go after one vertical - think JDate but maybe for the younger/tech crowd.
Actually, I think that one of the big problems with dating businesses is that if you're doing a great job you actually loose customers. This may be why no one does a very good job of it.
I think the problem with dating sites at the moment is that they make it easy to lie. If you've ever used Match.com, or something similar, the dates tend to end up poorly because one person who claimed to be into music listens to the radio on the way to work, while the other person who claims to be into music has a Masters from the Royal Academy of Music, has played in professional symphonies and spends eight hours a day practicing. Also, that is NOT and athletic build.
Now, if you monitoring their streams (Facebook, Twitter, MySpace, whatever), you could determine what they liked, where they went and who they knew. I suspect this is way better way to form meaningful connections (it's how I found the love of my life). And if you're just looking for a random hookup there's always craigslist.
I've been looking for a co-founder for the Y Combintor summer 2010 session - http://ineedacofounder.wordpress.com - so if you're interested hit me back and maybe we could team up.
Maybe the reason you didn't get an answer is that they weren't interested in selling - you don't respond to every random email you get do you?
It was fun to build and gave me a good look at Twitter oAuth and the APIs but I doubt it'll take it any further than it is already. I do use it on a fairly regular basis, as I'm kind of forgetful, and it does work pretty well so who knows.
I think where this really comes into play is now there are literally armies of iPhone developers in India and elsewhere (where there are lots of .NET programmers). The cost of iPhone app development should come down considerably.