872 karma · joined June 14, 2012
We'd love to know what you think. If you'd like to use the service just drop your email on our site. Thank you.
Thank you for writing.
Thanks for the feedback about the landing page. We're trying to make the documentation and API as simple and clear. Thank you for your comment.
I would be interested in what makes a kickstarter campaign click. The other side of the coin which is equally important is to find out what makes a campaign fail and the lessons that come out of that. Could you please also interview some folks that were unable to reach their pledge and how they felt they could have amended their approach ?
This is a good cheat sheet.
Like the others have mentioned here, there are a couple of tools in chrome that try to solve the same problem. Not that it is a bad thing. Has anyone used them all to summarize pros / cons ?
For example, you can find this behavior when someone posts something about problem X and there is a minor grammatical mistake or an opinion that is expressed in the post that is unconventional. The comments section will zero in on that and miss the big picture.
You can still surround yourself with smart people while freelancing. It is just a little harder to do. You also appear to be scarred by the experience which is why you never want to do it again. Good luck with the new job.
These metrics do not really reflect the heap sizes used in production, so I would not conclude that java does not need much memory. If anything, those that use Plumbr in evaluation mode do not run their JVMs with large heaps. You do not need a large heap to cause a OOM.
Still, it is interesting to know what the Xmx settings are on these boxes.
1 - http://mashable.com/2013/03/18/500000-google-reader-users-mi...
I would not hide the keyboard for any reason. It can confuse people pretty easily. If I try to click a button on a website and end up typing a character instead, it can drive me nuts.
Cool concept.
Pros
1. Expose your data through an API without writing much (any ?) code.
2. Time saving.
3. Since the API itself is fed by the framework, the opportunity for bugs is limited.
4. I can think of some people / businesses that would pay for this service.
Cons
1. I cant quite get why a service like this would limit its requests / month [1]. My take on it was that you are selling the transformation of the data into a service - as a service. I guess the calls / month is to also benefit from the value that your service adds to the data ? Number of calls made might not directly translate to value.
2. You are limited to relational models.
3. There are tricky conditional requests / data munging / orchestration etc that REST services are expected to take care of sometimes. It can quickly become messy if a client wants this. Is there a translation / conversion layer that can be inserted between the API and its caller ?
Some feedback...
1. Is there some way a developer can try this out before pitching it to a product manager or a higher-up ? There seems to be no direct way to do that. All plans under pricing are tied to money so some folks might be averse to signing up. Most devs just want to download and hack something out to show someone what a product is capable of. The dev can be your marketer within a company.
2. The layout of your site is neat. The call to actions are very specific and targeted.
3. I think your product has the potential to be awesome. Good luck.
- 'Submitted my YC application despite the storm' :)
* The layout of the pricing page is odd. Use the plan name as a column instead of a row. Most folks are used to seeing it that way - https://drone.io/pricing
* Do not start by showing the user a free plan. Users scan a page from left to right. Don't give them something they will easily choose right away.
* Get yourself a 'features' page that highlights what you offer in bullet points.
If you can say that without losing your breath, 1-up to you :) 'The easiest way to share your project status' seems like a better tagline. I like the simple layout. The colors are pleasing and easy on the eyes. I would still use another tool to show progress since not all progress may be tied to a UI.
1 - This is some sort of a marketplace where you can buy and sell expertise. Kinda like a Air bnb for odd jobs. Reminds me of a similar startup that tried that, but I cannot remember their name.
2 - The landing page's layout is a little confusing. I clicked on a couple of links and landed on your about page[1]. When you have a 90 second video explaining what your product is, why would you not put that on a landing page ? The call to action would be very easy for me. Click on the video and know more about you.
3 - Although you meant for people to click sign-in on the landing page, that action was not very obvious to me. You should look to prioritize 'Sign-up' not sign in. The fact that they are both green buttons that look alike does not help.
4 - Your key customer sign-up categories appear to be a buyer who gets services and a seller who markets his / her services. You might want to streamline signups to reflect that.
5 - The text overlay on the image is not very visible / readable. Have you considered switching the images to color on mouse-over ?
6 - Where is the submit button for 'Suggest a feature' under watercooler ?
7 - I don't quite get the watercooler part. Is it meant for users to share insights and that becomes part of the news ?
8 - What is your pricing ? Where can I see what cut you take and what I get in return ? What are people signing up for ?
9 - When I sign up, its not very clear to me that something happened on the screen. Its great that I am logged in, but the UI needs to do more to inform me about what just happened.
10 - A short tutorial on signing up would be great. The app asked me to add funds and I don't understand what for.
I like the idea. The presentation and the user flow could use a little work. Gather the feedback you get here and fine tune your site. Nice work.
I don’t want to build an application for your service.
I don’t want a relationship.
I don’t want to talk to any business development people.
I don’t want to read your developer blog.
I don’t want to participate in your “ecosystem”.
I don't recall any API agreement that dictates any of those. No one is forcing you to read a blog or change your relationship in facebook to 'in a relationship with twitter API'. I don't get this.
I don’t want to get an API key.
Fat chance. Some APIs need rate limiting / authentication. What do you have against obtaining an API key ? Its not that complicated. Most APIs provide BASIC auth or let you get OAuth tokens.
I don’t want to read your code samples.
ಠ_ಠ
What likely happened was that you were pissed with the API that someone provided. It had complicated requests where HTTP methods and simple structures alone were not enough to describe the request and to add to that you were given a freakin complicated way to retrieve auth tokens. You then decided to take it out on all API providers without providing enough context on your rant.
[EDIT] - formatting
Developer time is more valuable than hardware costs hands down. The horse power that you can back in return for that hardware cost varies between apple and windows.
"Global Apple App Store revenue is set to increase to $4.9 billion in 2012, up from $2.9 billion in 2011, according to an IHS Screen Digest Mobile Analyst Commentary from information and analytics provider IHS (NYSE: IHS). This means that nearly half of the revenue generated by the App Store in its five-year history will be earned this year alone."
Those are some pretty strong numbers. Given that the number is projected, even with a generous error rate of +-20%, any revenue from developer fee will be eclipsed by 4.9 billion.
While the author's estimate that apple generates 15% of its revenue from developers is inaccurate, it has to be said that the entry fee to get into iphone / ipad development is high. I would know since I'm currently developing a product that works across iphone / android / web. Here are our costs thus far (excluding phone-device prices ).
Apple:
Mac Air 1200$
Developer account 99$
DUNS number 200$
Server certificate for notifications 175$
Android: Developer account 25$
<For development - Use the mac or boot an old clunky win laptop with Win-XP on it>
Web: 0$ so far
Developing for apple devices is costly. For the same 1200$ that I could spend on mac air, I can get 2 powerful Win-7 laptops - ~ 500-700$ each [2]. Device fragmentation on android does require you to test on more devices, but there are services[3] that allow you to work around that problem. Besides, when netflix can release their app by testing it on a subset of 8 android devices [4], I don't see why that strategy is not good enough for others.
The author does have a point, but one that should not have been expressed as a percentage of apple revenues.
[1] - http://www.isuppli.com/Media-Research/News/pages/Maps-and-Pa...
[2] - http://www.dell.com/us/soho/p/vostro-laptop-deals
[3] - http://stackoverflow.com/questions/1852248/is-there-an-andro...
[4] - http://techblog.netflix.com/2012/03/testing-netflix-on-andro...
[EDIT] - Formatting