The problem is that the developers of autohotkey for Android only work on the emulator, which means that if you want to use the SDK for your own Android-powered app, you have to use it directly from the APK. This means that you won’t have a very well-documented API for the developers to use, which is a major problem, especially if you want to take advantage of the SDK’s features (like getting your autohotkey app to update automatically).
The problem I have with this is that this doesn’t mean you can’t write your own autohotkey for Android. The developers have made a few apps for Android, like the Autohotkey app for Android, that can be used directly from the APK. However, their APIs are still very limited, and there’s no guarantee that their API will be stable or future-proof.
The developers are aware of this, and are working on a second generation of autohotkey apps. With a few minor tweaks they can create an API that will be fully future-proof, stable, and customizable.
Android is a platform, and autohotkey is just part of the platform. You can use autohotkey on any platform, as long as you’re willing to pay the developers. Autohotkey isn’t free, but it’s not a commodity. However, if the developers are willing to invest some time making their apps easier to use, and more stable, they may be able to make some money on the market.
You can do autohotkey on both iOS and Android. The problem is, Android has a lot of hardware support. For example, as far as graphics cards go, the Nvidia Tegra 2 is available in Android. Google’s own hardware support is relatively low, but you can get a few devices with them under the hood. Android 4.0 Ice Cream Sandwich is a lot like iOS 3.
Android 4.0 Ice Cream Sandwich is like iOS 3, but with a lot more software features. Google is slowly adding features to it, but it’s still pretty limited compared to iOS. Android 4.0 also has a lot of power-users. For instance, developers can choose to make apps run on the Google Play store, or they can create apps that run on the Google Play store too. For example, the first version of the Google Reader app was a Google Play app.
Google is really the most interesting Android developer, since it is the one that is most interesting to developers. The reason Google is so heavily involved in Android development, is because Google has more users than ever before. Google has a very real presence in the Android world, but they are not always as engaged as they were in the iOS world.
Google’s role is to find good apps for Android in just a few days. For example, Android has a very good Android-supporting app that lets you get your phone in a few days. Google’s job is to create apps for Android that are relevant to the Android market. Google is more interested in apps that are relevant to the Android market than Android apps.