SlideIT keyboard for Android

If I were to ask you how else you would type without really typing on the keyboard, you may think hard and finally say you will voice dictate.. Thats the way Apple is taking us with Siri.

It's going to take some time before we effortlessly speak to our phones. But if you had thought there was no other way, then you need to think hard again in innovative ways again.

Please welcome SlideIT, the fun and in some aspects the easier and faster way to type.

In fact, I have been typing this post using there SlideIT keyboard! I love swiping my finger across the keyboard to type the text you want.

The concept is simple, all you need to do is connect the letters forming the word and SlideIT is smart enough to complete the word for you. The prediction is very impressive. And when you are unable swipe, you can always type like in a regular keyboard.

I am thoroughly enjoying typing in it for some time at least in this new way.

Now, some annoyances are, you'll have to remember where the keys are located in the keyboard. Second is, you can type only in one hand, which is quite obvious, but you'll have to use your index finger to type while holding the phone in there other hand, which makes it inconvenient to type while driving and similar situations!

Watch this video to see the typing in action.

http://www.youtube.com/watch?v=229U0ZYPum8&feature=youtube_gdata_player

Go ahead and try it yourself!

# tweetit

Blogger app on Android

One of the reasons I found for writing less on my blog is due to the unavailability of my laptop.

I had two laptops and both are broke now..  My 2 year old broke them.  Even when I had them, It was used by my family. I do have an iPad, but again the same case.

I was thinking about the resolutions I had made this year (My resolutions for this year deserve their own post later) and I just realized how miserably I had failed in the one where I had promised to write at least one post a week.

The last I wrote was around 11 months back.

That was when I thought "hey, anyways my online life has moved to my android smartphone.. Why not just use it for blogging as well!" 

But long blog post are not easy on a smartphone. Smartphones are definitely useful for micro-blogging such as twitter and Facebook updates.

I found that there is an app available for Blogger and just installed it to give it a shot.

In fact, I am writing this post using it.

The app is descent enough. Doesn't have a lot of editing options though.

For example, I still haven't figured out a way to enter images between text.

Also, doesn't show my existing labels.. I will have to type them manually :-(

Definitely not easier to type long post on a smartphone. Thanks to the SwiftKey keyboard, some of the typing pain is reduced by prediction and auto-fill.

Still I think PCs are best for regular blogging. 

Now let me post this to see how this shows up in my blog!

Is Sun getting desparate not to lose mobile JVM market?

After Apple announced last Thurday of its intention to release the long awaited SDK for iPhone*, Sun has unveiled its intention to port JVM onto the iPhone.

Its looks like Sun does not want to waste any time bringing the mobile version of JVM (J2ME) onto the iPhone. Obviously this sense of urgency should be due to the fact that iPhone provides a very good platform for mobile applications and also because of the impending threat from Google's Android. Sun should already feel frustrated by Google's clever coup of replacing Sun's JVM with their own.

The way I see the future is that Apple and Google may be in a direct collision course towards mobile dominance. And Sun may want to be present in one of the camps.

What also remains to be seen is how would Sun JVM affect Apple's business model of trying to sell iPhone applications through their iTunes store (App Store as it may be called). With the JVM present on the iPhone, would mobile application developers like to leverage it or will they rather choose to directly use iPhone SDK. With Apple bringing in restrictions on the development platform (only Mac can be used has the host to develop and debug iPhone applications), it gives a point of leverage for Sun.

And what about performance! iPhone SDK is already a layer on top of the native iPhone OS APIs. Now JVM would be one more layer on top of it. Will the java applications written for iPhone in future have the same performance as other platforms?

The war for a mobile computing platform is going to get interesting as days go by. Keep watching this blog to see how this unfolds.

Useful Links:
* You may be interested in reading this coverage of the iPhone SDK Press Release by Ryan Block of Engadget.
- You can also watch Apple's official video on the iPhone SDK Press Release here. Note: You need quicktime player.


[Article imported from Mobile Computing Trends]

Are you writing Java Apps for Android ? Maybe and Maybe not

Lot of people who are aware of Android think that they actually write mobile applications using Java. This is only partly correct.

What many people miss out is the fact Google Android uses ONLY Java Syntax. The java code that one develops for Android is converted in to standard Java bytecode. This again is converted in a different bytecode format (which Google claims that is an optimized, minimum memory footprint bytecode).

Basically, Android does not use a standard JVM (it uses a non-standard JVM called Dalvik) . The SDK also contains android.* packages apart from the usual java packages.

I found this post from Stefano Mazzocchi very interesting. He claims that the reason for Google using a non-standard JVM is not really for just optimization sake, but instead to get around any licensing issues with Sun for using J2ME. Wow! I never thought of that.

Its natural. If I were to run the Android project (instead of Andy Rubin), then I would start using J2ME as a preferred virtual machine for obvious reasons that we have a huge group of developers who can be readily moved/attracted to developing applications on Android. And then when it comes to licensing, I would think of someway to circumvent the problem and the one smart way is to make sure the final bytecode is not the same of the one generated by the standard java compiler. Thats exactly what Google engineers have done by developing Dalvik.


Other interesting links:
http://wireless.itworld.com/4269/071116googlesun/page_1.html
http://www.oreillynet.com/onjava/blog/2007/11/dalvik_googles_tweaked_nonstan.html

Wow!! Android Phone is a reality!!

Wow... I read this news at Phonemag.com about a Chinese company called E28 (haven't heard of it.. me neither) showcasing a real quad-band phone with wifi that runs on Android. Its available for sale.

Look at the video below to believe it :).

Android is going to give big mobile OS players like Symbian and Microsoft a run for their money. As I can see, smaller and unknown mobile phone manufacturers from around the world are going to benefit from open-source and freeware mobile phone operating system stacks. They will not have to worry about paying royalties/licensing fee for running a proprietary mobile operating system.

And last but not the least... WOW!!

Videos about Android!!

I was surprised to find very good videos in Youtube explaining about Android. Most of these official videos could be found under the username androiddevelopers.

Here is my favorite video from Sergey Brin and Steve Borowitz where they give a nice demo of Android features.

What makes you browsing experience in iPhone and Nokia N/E series phones great ?

You should thank Webkit, the open source web browser engine*, for the wonderful browsing experience.

This what the Webkit home page has to say:

WebKit is an open source web browser engine. WebKit is also the name of the Mac OS X system framework version of the engine that's used by Safari, Dashboard, Mail, and many other OS X applications. WebKit's HTML and JavaScript code began as a branch of the KHTML and KJS libraries from KDE. This website is also the home of S60's S60 WebKit development.

Apart from Apple (as the Safari web browser in their Mac OS X, iPhone and iPod Touch) and Nokia (in their N and E series of phones), Google has also included Webkit as the default web browsing engine in its recently released Android platform for mobile devices.

In his post, Bob Cringely reasons as to why Webkit is such a strategic project for Apple and why it would also be the driver for the rumoured iTablet (you find my previous post questioning as to whether Apple's PDA would click or not ?).

You may also find it interesting to read this post by Om Malik about Webkit's rise to popularity. Gives you a quick round up of where webkit stands compared to its competition.

Webkit is still evolving (but fast) and has a long way to go before winning hearts of hardcore Opera Mini fans like myself :). Read this post in Wap Review to know why Opera Mini 4.0 is better than Webkit on a Nokia (and I completely agree with that).

-------------

Web Browser Engine - This is the piece of software which downloads the html web page from the address specified by you, processes it and renders it back on the screen of the display device. The screen could be anything from your PC Monitor to an iPhone's touch screen.

How does Google benefit from Android?

This was the question my friend and office colleague was asking me when we were, in general, discussing about technology.

I explained to him that Android will speed up innovation on the mobile computing front thus ensuring that users have a better and more PC-like web browsing experience on their mobile devices. This ensures that more and more users will starting browsing the net from their phones and thus ensuring that more and more traffic is driven to one of Google's many services where they serve Ads and also not to forget that Google Ads are scattered all over the world wide web.

Basically, Google believes in increasing size of the pie rather than increasing size of the slice in the existing pie. Interesting quote isn't it :). Well, I read about this quote in this news article by Financial Post which questions Google's business model on going the open source way with OpenSocial and Android.

Though I told my friend about the above, I wanted to confirm again if this is how Google really was hoping to benefit out of Android platform. So I did a little bit of Google'ing and and came across this interview given by Eric Schmidt and Andy Rubin, Director of mobile platforms at Google (the brain behind Android)

This is what Eric Schmidt, CEO of Google, has to say in his interview at PBS.

SPENCER MICHELS: Now you say you're almost giving this away, why?

ERIC SCHMIDT: We're giving Android away because we benefit when the Web is better. We benefit when more people are using the internet, especially on mobile devices. And we benefit because when more people use Google, more people use Google search and every once in a while those people will use our ads. So eventually we think an Android mobile user is pretty likely to use Google advertising and our studies indicate that mobile ads are going to be worth a lot more than the traditional ads that we sell.

SPENCER MICHELS: Why?

ERIC SCHMIDT: The easiest example to think about is how personal your phone is. Everyone here, everyone in our audience has a mobile phone, very hard to get away from them. That phone is with them, it knows where they are. Imagine how we can use that information to provide a more targeted ad, if it were appropriate.

By the way, it is a very good interview and would recommend reading it if you want to know Google's plan for Android and mobile computing.

Google forming the Open Handset Alliance and defining a new mobile platform called Android once again proves my point that there is this race to establish a linux-based mobile operating system/platform (Oh yeah.. Android is based on Linux. On top of Linux, they have a Virtual Machine which offers APIs similar to Java VM but is supposed to be much more advanced than Java VM).

But with Google intelligently forming an alliance which includes telephone operators to handset manufacturers to chip manufacturers, they are better poised to take over the Mobile Operating System space much to the dislikes of giants like Symbian and Microsoft.

Google not just stops there. They even have a announced a $ 10 million prize money for users who develop useful and compelling applications using Android. This is to ensure that more and more developers get involved in this effort.

The advantage, I could perceive, from Android could be the following:

Handset Manufacturers: They would not have to pay hefty licensing fees to proprietary mobile operating systems like Symbian and Microsoft. So the cost of the handset goes down thus boosting the handset sales.

Developers: Because it is an open platform and almost everything is available for free, you can pretty much write any application you want. Imagination (of course the phone's capabilities) if your limit.

Consumers/End Users: Because handset prices go down, consumers can afford to easily buy them and they also get to install and use thousands of applications that were developed by the open source community.

Telephone Operators: They get to benefit because consumers start using these web-enabled/web-based applications on their Android phones and thus the data traffic is going to increase drastically. Operators are going to charge for this data traffic.

Of course, not to forget Google (and others).. they would be benefiting as well from Ads clicked by users on their mobile phones.

I am not sure how successful Android is going to be. But my gut feeling says that it will take off well. But, I believe, for the mobile web to pick up really well, the network speeds have to improve a lot. They sure will. Its just a matter of time.

-----------------

For those read this post till this point, scratching your heads, wondering as to what Android was all about, please read below.

Google, earlier this month (Nov 5th, 2007) announced that it was forming the Open Handset Alliance which is going to drive the development of Android. Android is an open platform for mobile phones which consist of an operating system, a set of software modules for performing some of the common tasks on the phone (middleware, as we call it in software terminology) and a user interface. You also can download the software development kit (SDK) for developing your own applications that run on the Android platform.