[TIMOB-1466] Support for Android notification bar
GitHub Issue | n/a |
---|---|
Type | New Feature |
Priority | Trivial |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2011-04-15T02:53:39.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Android |
Labels | android, feature, notification, status |
Reporter | Ralf Pfeiffer |
Assignee | Don Thorp |
Created | 2011-04-15T02:53:38.000+0000 |
Updated | 2017-03-10T18:20:03.000+0000 |
Description
Many Android apps notify the user of an event by a Notification Sound/Vibrate and then they put an item into the notification/status bar where the user can easily retrieve it.
Examples of apps that use this:
Gmail - incoming mail triggers alert. User pulls down notification bar and sees new messages, click to view
WeatherChannel - constant icon in notification bar to show temperature of chosen city
IM/Chat - number of new messages shown/status etc
Access to this seems to be missing from Titanium, I think it would be a very valuable addition. Increasingly Apps monitor situations and provide instant feedback to the user is very important. I realise that there are other ways to notify the user, such as by using an Alert or Ti.UI.createNotification. Both of these create a visual interruption in the screen which take focus from what the user might be doing. Also once these alerts have gone the user cannot then find what the notification was.
I don't know if the iPhone has a similar paradigm.
I am in the same situation. i need android notifications with titanium. i am using Titanium 1.5. is it possible with Titanium 1.5?
Looks like it might be in 1.6: http://developer.appcelerator.com/apidoc/mobile/1.6.0/Titanium.Android.createNotification-method.html"> http://developer.appcelerator.com/apidoc/mobile/1.6.0/Titanium.Andr...
This is in Titanium Mobile 1.6.0. It was implemented by #2091 #2835 #2738 and several others around intents and pending intents.
Here is a sample of how to use it:
https://gist.github.com/855834">https://gist.github.com/855834
Closing ticket as duplicate.