Android Push Notification: Deprecating MQTT in favor of GCM

Two photographs of colored pencils and a paint brush combined to form a new object.

We are pleased to announce the support for Google Cloud Messaging (GCM) for Android. We are also announcing the deprecation of current MQTT push notification service in favor of new GCM push notification service.
Appcelerator Cloud Services (ACS) has been supporting MQTT based push notification service for Android devices. Google released Cloud Messaging Service (GCM) last year that meets customers’ most demanding scalability requirements while delivering better battery life and resource usage. GCM also offers new push delivery options and support for Android Rich Notifications, which can deliver images, more text, and drive users to actions like making a phone call, sending an email, opening a web page or playing a song right from the push message. We will add new features only for GCM service going forward.
We are supporting both MQTT and GCM (default) services with Titanium 3.1.2 release but we strongly recommend you to use and migrate to GCM service as we will discontinue MQTT support later this year. You can download the latest ACS Android SDK if you are not a Titanium developer. Please refer to ACS Android push documentations to get started.


Please post your questions on Appcelerator Q&A forum with “ACS” tag or leave your comments on this blog post.

Previous articleCallbacks in Appcelerator Titanium Modules
Next article5 ways to transform how you work


  1. When you say “we will discontinue MQTT support later this year,” can we still assume that Android apps created in previous versions of Titanium using MQTT will still continue to work fine even after that?
    Is there any possibility of continuing to support both push variations going forward so that we do not have to re-write code that is already working fine with ACS MQTT? If we are happy with the level of functionality provided up to now with MQTT could we have the option to stick with that service and only migrate to GCM if/when we actually needed the additional features it provides?
    Also, will an updated Kitchen Sink or a complete working Android code/app example with the new GCM push implemented be provided soon so that we can better understand exactly how to migrate an existing MQTT app over to the GCM service?

  2. I just noticed this on my ACS Panel – “MQTT support for Android push notifications will expire on December 31st, 2013. Please upgrade your app to use Android GCM”
    Will I be able to continue to use MQTT after that date? I REALLY need this as most phones in China do not support GCM – I believe you will loose a large community of people if you completely remove MQTT as there are alot of app developers developing for China who use MQTT.
    Please let me know if I will still have the MQTT functionality after Dec 31st. If not I do not know what I will do to enable push notifications to users in CHINA?


Please enter your comment!
Please enter your name here