I don’t think any API can beat Qt’s signal/slot mechanism. Try to compare the way how events are handled in Android API.

Chuck.Gao wrote:

what’s the differences between Qt and Android development

In my opinion there are too different to compare. Android is OS for mobile devices and Java is used for application development while Qt is C++ framework compatible to different OS (including Android :) )

situ117 wrote:

I don’t think any API can beat Qt’s signal/slot mechanism. Try to compare the way how events are handled in Android API.

I have no idea about how event are handled in Android, but i think it’s event driven also.

leon.anavi wrote:

In my opinion there are too different to compare. Android is OS for mobile devices and Java is used for application development while Qt is C++ framework compatible to different OS (including Android :) )

Yes, it’s true. And how about think it from APIs point of view? Just the interfaces, do you find some limits in Qt ?

Well, there are two major points in using Qt as I see it.

1. Platform independent. You can write code for multiple platforms using the same code base. It’s not dependent on having a specific OS installed. Android code can only execute in a dalvik/android-environment.
2. Language independent. This is even better than the first point, at least for me. You can choose to develop in many different languages such as Python, Java, C#, Ruby and C++ (and there sure more options). Android is basically Java-only. I’m sure their scripting supports are actually executing by the dalvikvm.

Then I would also add that the Qt-api:s feels more generic and Android is more tailored for specific situation where you need to embedded contact manager, calendars etc in your application.

C# for Qt? Really? Is there a C# prot?

http://code.google.com/p/qt4dotnet/
http://techbase.kde.org/Development/Languages/Qyoto

I’m not sure of the status because I’m not using C# but it seems to be a rather small community behind the C# bindings.

I think the python bindings has the best support

mario wrote:

Well, there are two major points in using Qt as I see it.

1. Platform independent. You can write code for multiple platforms using the same code base. It’s not dependent on having a specific OS installed. Android code can only execute in a dalvik/android-environment.
2. Language independent. This is even better than the first point, at least for me. You can choose to develop in many different languages such as Python, Java, C#, Ruby and C++ (and there sure more options). Android is basically Java-only. I’m sure their scripting supports are actually executing by the dalvikvm.

Then I would also add that the Qt-api:s feels more generic and Android is more tailored for specific situation where you need to embedded contact manager, calendars etc in your application.

Yes, a lot of language bindings. And as you says, Qt is more generic, you can use it create more beatiful things, while Android, i think maybe it’s a little bit tailored. But, anyway, it depends.