106 karma · joined October 4, 2011
Re the design, all I meant by too much work is that I actually needed to look for where to buy. It's obviously a clean set up, there's just not much information that shows up above the fold that makes me want to scroll down (it was the comments in this section and the title of this post that even got me to your page). But yeah - obviously you've thought through it and it's your thing. Good luck with it!
The design of this page is sort of hard for me to get through - I know you intentionally made it informal, but maybe something to consider.. I'm a huge fan of the products you've designed, but not a fan of this layout for presenting the book. Specifically, it's way too much work to find the area to buy it, and there's no real call to action (or clarity) above the fold when the page first loads. The unicorn insults thing - feels like you stumbled into an inside joke, not an incredible ebook by an awesome designer. Just my $.02, I'm not sure if you were even looking for feedback on that but figured I'd share.
Looking forward to downloading it!
I do like the idea of a codecademy for social media as a way to generate future paid users, you just may need to reconfigure the flow. The social media tutorial piece of this is great for buzz, but ultimately it sounds like your main product is the one for community managers, and those are the people who will bounce the second they think your site is going to teach them how to create a twitter account.
One way or another the experience will be valuable (learning to manage/work with engineers is just as valuable as coding IMHO), but again - don't spend that much to do it. You could build the prototype, only to find that it's not a service people are interested in using. That would suck, but not as much as losing your entire savings to learn the same thing.
Next logical step is tapping into API's for settings API's have control over so you can streamline the settings update (obviously that will never be completely possible for usernames/passwords etc - but the more social apps and customizable settings out there the more of a pain point that will become).
One caveat - knowing how to photoshop is different than knowing how to design. UI/UX is a completely different subject.
A total pet peeve, but the companies who send these confirmation emails are the same ones who make you jump through ridiculous hoops - with all the trouble they make you go through to unsubscribe, how could it possibly be a mistake?
Hopefully this ends fast.
1) Creating the app is half the battle - executing on distribution is the main thing you'll have to fight.
2) You don't know what their end game for the app is - they might be creating it with a totally different function in mind. So even though up front you may think they've created something identical to what you are, that might not be true.
3) The fact that there's another app out there that does what you are planning on doing further validates that you have a great idea.
4) Don't be concerned with competitors. Phil Libin from Evernote said it best - on the list of top threats to your app's ability to succeed, a competitor's success doesn't even register.
But outside of that advice, someone needs to build this!
Understand things from their point of view: they're a popular company in a popular area. They probably have so many resumes being sent in that it's tough to manage the flow, and at junior positions like interns, it's difficult to differentiate candidates. One core differentiator at pre-entry level positions is ability to learn - and that's something that isn't too easy to pick up on in a resume.
Their loss is another company's gain.
If you're meant to end up working there - you'll end up there. Sometimes it's out of your hands, but there are enough awesome startups in New York that you'll get picked up somewhere fast.
And if you don't get the job, once you're tremendously successful a few years from now - you can always send Dennis and Naveen an email letting them know they missed out :)
Only reason I mentioned this is that it brought the essence of the article out in one sentence (tl;dr).
Please either delete my comment, let me delete my original comment, or stop downvoting me. What's the point in downvoting someone repeatedly? I'm not sure how the system works on your end (or if you can see how many others have downvoted), but seems pretty harsh to keep doing this when there was an honest mistake. Thanks.
I think the main flaw with this idea is that everyone wants to make accounting "simple." Unless you are going to focus on a specific niche, I think you're not going to solve the problem.
It sounds like you want to solve the problem of visualizing accounting data better than any other product or service. Why not build an app that works with the quickbooks API (Bill.com is the most notable app out there that sync's with QB). Just an idea..
There's enough on linkedin to give you most of the information you'd need to graphically show hiring trends - many profiles are public, you'd get more than enough info to see what people are doing (profiles typically have college, grad year, and positions they've held).
Gmail has an alright workaround - they manage to hide the content they view is copied from a previous message.
I don't know if explicitly breaking the thread would do anything - usually when a thread gets too long, I just change the subject line, problem solved.
You haven't been too specific about what you're trying to do, so there's not much else anyone can do to help without more information.
What exactly are you trying to accomplish?
The writer lost all of his credibility once he dropped that line.
Are you caching the data? It would be cool to see a graphical interface of this over time. The guys at insidefacebook have done a nice iteration of this idea on the analytics of facebook apps and pages (http://pagedata.appdata.com)
It would also be cool if you could somehow integrate Compete and Quantcast into here too (not that any of those three are terribly accurate - but would be fun to look at).