My daily readings 06/02/2010

  • tags: Education

    • You can also contrast this information with Cleantech as a category. From a KPCB presentation I attended earlier this year, apparently Cleantech as a category is roughly a $6 trillion industry. And you have $5-6 billion on average invested by VC’s every year.

      Contrast that with the Education Category where you have a max of $100 million chasing a $2 trillion industry. So that means that Cleantech investors are chasing a 3x larger market than Education and yet are putting 50-60x the money to work chasing those returns.

      The numbers make this conclusion a no-brainer: there’s about to be significantly more venture capital investment in the Education category.

  • tags: Android

  • tags: Android, Compatibility

      • What It Means for You

        All that is great — but what does it mean for developers? Well, we put together a page in the SDK Documentation to explain this, so you should take a look there. But really it boils down to this:

        1. As a developer, you simply decide what features your app requires, and list them in your app’s AndroidManifest.xml.

        2. The Android compatibility program ensures that only compatible devices have access to Android Market.

        3. Android Market makes sure your app is only visible to those devices where it will run correctly, by filtering your app from devices which don’t have the features you listed.

  • tags: no_tag

    • So why is such zealotry a good thing? Because passion is important. If people actually care about Android that much, Google is clearly doing something right. Windows Mobile has never instilled this type of passion in anyone. Nor has Symbian. For a while, it seemed like the Palm Pre might. But it never did. But Android is.

      As I described at length last week, the rivalry between Apple and Google is going to be a good thing for us all. Part of that is because the companies are largely equals, so the fight will be fair. But don’t underestimate the importance of fanboys in this equation. For too long, Apple has gotten a massive amount of free fanboy publicity while many of their rivals have gotten none. Android is now starting to get that kind of free publicity too. All of this plays into the idea that the two companies will push one another to make better products, because again, they’re on equal footing.

      And Android Fanboys will make the Internet more balanced because they almost exactly counter the ideals (and now passion) of Apple Fanboys. Android Fanboys care about openness and choice. iPhone Fanboys care about presentation and experience.

  • tags: extension, firefox, Android

    • Besides the API they have published also a little project “Chrome to Phone” that adds a little button in your chrome browser to send whatever page you are currently viewing to your phone. But despite all the nice features of Chrome I still prefer to use Firefox, the Chrome interface still looks too weird to me and in general I know that I Firefox works mostly the way that I want.

      So the next step was quite obvious: it was a Sunday with some free time so I created the Send to Phone extension. It was funny but quickly after publishing it I realized that another guy had the same idea and he beat me by 3 minutes, fortunately it seems that none of us have a big ego so we have agreed to merge both extensions, I picked some of his code, added a few extra things and we got now a nicer version for you to enjoy.

  • tags: no_tag

      • Many of the Google applications on Android already use push to keep their data fresh, for example Gmail, Contacts, and Calendar. Starting with Android 2.2, C2DM allows third-party developers to use the same service the Google apps do.

        Here are a few basic things to know about C2DM:

        • It requires Android 2.2; C2DM uses Google services which are present on any device running the Android Market.

        • It uses existing connections for Google services. This requires the users to sign into their Google account on Android.

        • It allows 3rd party servers to send lightweight data messages to their apps. The C2DM service is not designed for pushing a lot of user content; rather it should be used like a “tickle”, to tell the app that there is new data on the server, so the app can fetch it.

        • An application doesn’t need to be running to receive data messages. The system will wake up the app via an Intent broadcast when the the data message arrives, so long as the app is set up with the proper Intent Receiver and permissions.

        • No user interface is required for receiving the data messages. The app can post a notification (or display other UI) if it desires.

      • On the server side, your server needs to get a ClientLogin Auth token in order to talk to the C2DM servers. When it wants to push a message to the device, it can send an authenticated http POST with:

        • Authorization: GoogleLogin auth=<auth token>

        • URL encoded parameters including the registration id, the data key/value pairs, a “collapse key” used for overriding old messages with the same key on the Google C2DM servers, and a few other optional params.

        When you use the C2DM service, you no longer need to worry about dealing with flaky mobile data connections, or when the user isn’t connected to the internet (i.e. Airplane mode). C2DM keeps the messages in the server store, and delivers them when the device comes back online. Basically, you can leave all the hard work of designing a robust push service to Google. Your application can take advantage of push infrastructure we’ve already built and tested, and stay more connected to the internet. Best of all, you won’t ruin the users’ battery life.

        Information about how to build C2DM enabled applications on Android is online at the code lab, and more will be coming as we approach general release.

      • To enable C2DM, an application on the device registers with Google and get a registration ID, and sends the ID to its server.

      • When the server needs to push a message to the app on the device, it posts the message via HTTP to Google’s C2DM servers.

      • The C2DM servers route the message to the device, and an Intent broadcast is sent to the app.

      • The app is woken up to process the message in its Intent Receiver.

      • The app can unregister with C2DM when the user no longer wants messages to be pushed to it.

  • tags: Chrome, extensions, development

  • tags: iPhone, app

  • tags: Javascipt

Posted from Diigo. The rest of my favorite links are here.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: