The fragmentation in the Android development sphere should really keep most developers off that platform until long after they’ve reached that successful stage.
Let me state up front that I have no problem with Android and see its own benefits. But in this context, startups should follow the lead of Instagram and only start dabbling with Android if and when there’s a solid base of millions on iOS and/or if it becomes a strategic chip for the startup.
I’d like to see a breakdown between iOS and Android users. I probably download an average of 3 apps per month. And most of those would be paid. If you factor in the free games and things my kids download it probably goes up over 10.
I love this kind of stuff. Even if it’s presentation is a bit of the click-bait kind.
40 maps that explain the Roman Empire
Not a bad looking toolchain for spinning up your web development projects. Definitely something to keep in mind or keep an eye on.
Rec Room is a Node.js utility belt you can wear to build client side web apps. It includes:
Brick to add components like appbars and buttons to your UI.
Ember for your app’s controllers, models, and views.
Handlebars to write your app’s templates.
Grunt to run the tasks for your app, including building for production.
I18n.js to localize your app.
Mocha to test your app.
Stylus to write your CSS.
Yeoman to scaffold new code for your app’s models and templates.
Should be rolling out in the fall. Can’t wait! It’s also interesting to hear that Google will be rewarding HTTPS in search rankings.
First, Google just announced that they will begin taking into account whether a site supports HTTPS connections in their ranking algorithm. This means that if you care about SEO then ensuring your site supports HTTPS should be a top priority. Kudos to Google to giving webmasters a big incentive to add SSL to their sites.
I wonder how many of those subscribers continue paying just keep their email address and how many still use dial-up.
But as always, the most amazing thing about AOL’s business is the thing that drives AOL’s business: Millions of people, who started paying the company a monthly fee for Internet access more than a decade ago, who continue to pay the company a monthly fee for Internet access, even though they likely aren’t getting Internet access from AOL anymore.
Dan Rayburn breaks it down with some context and history and gets right to the point.
The reason for the poor quality streaming is that Cogent refuses to pay Comcast to add more capacity, even though Cogent is taking Netflix’s money for the service. Cogent is charging Netflix for a service it can’t deliver.
So, the deal with Comcast may not be as bad as it seems at first glance.
All the tools that the cool kids are using!
From the Wall Street Journal:
Netflix Inc. has agreed to pay Comcast Corp. to ensure Netflix movies and TV shows stream smoothly to Comcast customers, a landmark agreement that could set a precedent for Netflix’s dealings with other broadband providers, people familiar with the situation said.
This sets a dangerous precedent, but I doubt Netflix had any alternatives based on this:
Netflix Chief Executive Reed Hastings decided to strike the deal after Netflix saw a deterioration in streaming speeds for Comcast subscribers. According to Netflix data published in January, the average speeds of Netflix’s prime-time streams to Comcast subscribers had dropped 27% since October. Mr. Hastings didn’t want streaming speeds to deteriorate further and become a bigger issue for customers, the people said.