Google Cloud Messaging (GCM) no Android
Nesse vídeo mostro como utilizar o Google Cloud Messaging para enviar mensagens push aos usuários que utilizam sua APP. O Google Cloud Messaging ou apenas GCM é uma serviço de mensagens push do Google, e a grande diferença desse serviço para os outros é a possibilidade de fazer com que seu servidor Web seja a parte ativa da comunicação, ou seja, o usuário de sua APP não precisa estar com ela em funcionamento para ser notificado sempre você quiser notificá-lo enviando uma mensagem partindo de seu servidor Web.
O GCM é composto na verdade por três níveis de entidades,seu servidor Web, que é responsável por enviar a mensagem junto com os IDs dos dispositivos ao servidor GCM do Google, o servidor GCM do Google que pode ser HTTP ou CCS (XMPP), e então os aparelhos com sua APP instalada e que receberão a mensagem. Com o servidor HTTP escolhido (que é o do vídeo), nós apenas podemos enviar as mensagens de nosso servidor Web para o GCM e então para os aparelhos a serem notificados, já com o servidor CCS (XMPP) nós também podemos enviar a mensagem partindo do aparelho para o GCM e então para nosso servidor Web, processo também chamado de upstream (ou outro que também é suportado pelo HTTP é o downstream). No vídeo mostro vários IDs e aqui já cometem me referindo no plural, mas vc pode trabalhar da maneira como quiser (enviando uma mensagem personalizada individual para cada usuário, ou para um grupo, e por ai vai). No vídeo mostro minha implementação PHP do servidor, note que a parte onde tem a lógica mesmo para definir quais dispositivos receberão a mensagem e quando remover um registration id inválido está no servidor Web, a parte implementada no Android é mais «decoreba» do que lógica. A implementação no servidor é totalmente sem padrão, ou seja, você faz a sua como quiser, porém você precisa salvar os registrations id para poder notificar os usuários e é bom também implementar parte do código para saber quando remover ou não um registration id do banco de dados (isso é mostrado no vídeo). Lembre que o registration id é uma vinculação de sua APP com o dispositivo, ou seja, se sua APP é do tipo das que tem login você terá de fazer essa vinculação na mão em seu banco de dados, que não será difícil, somente vincule no banco de dados o registration id ao user id no bd. Acho que é isso, vou evitar mais delongas e deixar você assistir ao vídeo.
O link para download do código do projeto (incluindo código PHP) se encontra logo abaixo no post, no blog (
Segue links dos vídeos que podem ajudar a compreender melhor as tecnologias utilizadas junto com o GCM:
BroadcastReceiver no Android, Executando Tarefas no Background (
Notification no Android, Criando Notificações Com Toque e Vibração (
SharedPreferences no Android, Entendendo e Utilizando (
Segue links das páginas apresentadas no vídeo:
Console de desenvolvedor Google (
Página de explicação do Google Cloud Messaging no Android (
Página Getting Started no Google Cloud Messaging no Android (
Página do GCM HTTP Connection no site do Android (
Página Implementing GCM Server no site do Android (
Página Implementing GCM Client no site do Android (
Código de 20% de desconto na Novatec (THIENGO
APP do Blog:
Siga no Google Plus: Siga no Twitter: Curta no Facebook:
How I: Customized push notifications to engage users
Hi, my name is Eren, and I'm the product manager
for Webnak, which is a logistics marketplace
application in Turkey.
Right now, through Webnak, we send a push notification
to all the truck drivers regarding the shipments.
So let's say if you have 100 shipments per day,
100 notifications go to all the truck drivers that
are registered in our system.
That may be good, or annoying, for some of them,
but it will be a problem when we have 1,000 shipments per day.
To fix that, we try to come up with an intelligent
We will look at the location of the truck driver
plus his or her interests.
If a truck driver is interested in a city, which
we see that from their previous bids,
we will send the notification to the truck driver.
Or, if he's close to the loading place,
if he's close to the destination,
again, it would be important for the truck driver,
so we'll still send the notification.
So these technological changes helped
us scale our business from 100 shipments a day
to 1,000 shipments per day.
It even– it will grow even bigger.
Sistem Terdistribusi Android Push Notifications menggunakan Google Cloud Messaging (GCM)
Sistem Terdistribusi Android Push Notifications menggunakan Google Cloud Messaging (GCM)
Dosen Pengampu Rohmat Gunawan
Iqbal Mulyawan Putera
Robby Iswanto Purtono
Kelas E 2013
Jurusan Teknik Informatika
Universitas Negeri Siliwangi
Source Code dapat diunduh melalui link
Platinum Elements (The Polymer Summit 2015)
So I'm Mat Scales, as Matt said.
And I'm here to talk about the platinum elements.
The platinum elements are our way
to help to make using the latest and greatest web platform
features easy with Polymer.
So the web is getting a lot of really cool features recently
and this is great for users, it's great for developers,
and it's also great for businesses
that want to be able to do exciting,
new things without tethering themselves
to a closed platform.
But it's also getting complicated.
There's a lot to learn now.
And realistically, you can't learn all this stuff any more.
Now these new features are actually,
they're so powerful because they're very deep.
So what can we do about this?
Well luckily, there's an element set for that.
So what we've done is we've created the platinum
element set and the idea here is that these elements wrap
these complex APIs and provide the most obvious use
cases simplified out so that you can just drop them in.
So the platinum elements, most of the features
that we're wrapping here are only
implemented in a few browsers, pretty much just
But the Platinum elements themselves,
if you drop them into your page, they
will just gracefully degrade if you use them in a browser that
doesn't support them.
All of these features are enhancements.
The traditional web has always happened in a tab
and these features allow you to break out of the tab
and do things outside of that environment.
So again, we're going to talk about offline, push messaging,
and device access.
So first up, off line.
So when I say off line, really what I mean here
is removing your dependency on the network.
So in order for your app to work offline,
you need to have all the resources for your app
on the device and this is a huge performance boost
even if you actually have a good connection.
There are lots of people who have no connection
for various parts of the day.
I commute through London on the underground train
and I don't get any connection there.
There are also lots of people with just bad connections,
so there's another part of my commute.
I go through the countryside on a train
and I have pretty bad 2G for big portions of my commute
and I live in a first world country, in a huge city.
So this problem only gets worse when
you go to remote places or emerging markets.
And I say this actually will improve the speed even
on a good connection.
You don't have to go to the network
at all for a lot of these things.
Now, a lot of people, they're not quite sure
how this will work for their app.
Surely it's on the web because it needs the network
and that's a good point.
So offline takes different forms for different applications.
So here we have a simple– this is actually a Google Doodle.
It's a crossword.
This can be entirely offline.
There's no online component here at all.
You put all the resources in Oracle cache,
you load them all up, and everything will just work.
So this is a very good case.
Something like Gmail, obviously, that's
network based, but there things you can use.
There is the app shell, all of the user interface,
the new message box here, and obviously, you
can cache messages that have already
been downloaded so that the user can still read to them even
And the same here applies to something
like a chat, app, or something like that.
And then worst case scenario, your app really,
really just needs to be online to do anything.
You at least can control that offline experience.
You can put up your own branding, your own message.
So by default, in Chrome, you get the little offline dinosaur
and if you click it, you get a game.
You could put your own game, something
to do with whatever it is that your business is about.
What does this have to do with Polymer?
Well, there's an element for that, specifically, platinum sw
or a set of platinum sw elements.
The sw here stands for service worker, as Matt said.
It's a new feature implemented in Chrome,
but it is coming to other platforms.
Mozilla have their implementation,
I believe pretty complete and it's in Nightly's and they're
just waiting to make sure it's absolutely stable,
and other browsers have shown great interest
in implementing this.
So how does this work?
Normally, you have a page and request resources
and it just goes to the network to fetch them.
With service worker, you add this intermediary,
this script that you've written, and any time the page
requests a resource, this could be the initial page navigation.
It could be images, scripts, CSS, or XHR, or fetch.
Service worker gets to say what to do.
And it can go to the network.
It can go to the server and fetch that if it wants to,
but there's also a cache API built
in with service workers and that stores request and response
pairs, so you can seat that cache
with the request for your resources
and then the response that you need
to give all of those resources and just
return those instead and never go to the network.
And now thanks to platinum restore,
you can get the benefits of using service worker just
by adding a couple of elements to your page.
So platinum has to be a register.
Here it just says, I'd like a service worker in my app.
That's not really going to do a great deal on its own,
but we configure it by adding some elements inside.
I don't know what happened.
So platinum sw fetch, allows you to say
how to handle certain kinds of resources.
So you see here that we've got this path.
So any time a resource is fetched
that matches this path or this path pattern,
we're going to handle it in a particular way
and you can set these up for as many different parts
of your site as you like.
Platinum has to be a cache, I'm just
going to point out this bit here first, the pre-cache.
This says to the app, as soon as you load this,
I want you to put all of these things
into the cache straight away.
These are the critical parts of my application.
So as soon as I load, put them into the cache
so that they are there for the very next time
that the page is loaded.
So here I've just got, as an example, index
to HTML and the CSS file, but you'd
you needed to show probably your home page and maybe
a shell of your app.
And I kind of skipped over this before.
So there's a handler in the fetch
and there's a default cache strategy in the cache element.
They're both set here to networkFirst,
but in there you put in what you want
to happen for these resources.
The one in the default cache strategy
is what should happen when the current resource being loaded
doesn't match any of your fetches.
So what's all that about?
So there are a bunch of different cache strategies
networkOnly is the simplest one to explain
because basically the service worker doesn't do anything.
It just lets it go straight through to the server.
networkFirst, so for that resource,
we try and fetch it from the server
and if that doesn't work for some reason,
then we'll look in the cache instead.
This is better than not doing offline at all,
but it's slightly problematic because that network
connection, if it's just a bad connection, it could take
two minutes for that to timeout, which
would be terrible performance.
So better performance cacheFirst.
If we have that resource in the cache loaded
straight from there, don't even consult the network.
That one is always going to be much faster for stuff
that you've got in the cache.
If it does go to the network, then when that's fetched,
it sticks in the cache for next time, so you can use this for,
we'll call read-through caching.
And then my favorite one is called fastest,
which basically, you go to the cache,
you go to the network, whichever one comes back first, use that.
Usually for anything that's in the cache,
this will be whatever is in the cache, not always, apparently.
But when that network request, because the network request
always happens and it always updates
the cache when it comes back, it means that you're
only one refresh behind.
So you're slightly still, perhaps.
And the even better one, I guess, is your own thing.
You choose the pave that you need for your application.
So we had one that was networkIfFastEnough.
So it would try the network and then
there would be a set timeout, which
is after 500 milliseconds.
It said, no, you're too slow.
Go to cache instead.
So you try and get the thing from the network.
So with these building blocks, we
can build all sorts of different applications or ways
of dealing with offline in your applications.
So simple read-through caching, you could set it
up so that you don't have any fetch handlers,
you have a default cache strategy of networkFirst
or cacheFirst, whichever you like
and every time a resource comes through,
it will try the network.
You have to go to the networkFirst,
but then it will stick in the cache and the next time,
you can get it from the cache.
So it will build up the cash as the user goes around,
but you don't do any pre-caching.
You can, obviously, pre-cache all your resources,
as I said before, so that most of your app works
offline straight away.
Some resources you'll have like huge a header image
or something like that.
Maybe you don't want to store large resources, videos
and things like that in the cache.
So you say those ones are networkOnly
and you can implement fallback media instead,
so by creating your own handler, and you can say,
for these resources, if the network is available,
get it from the network, otherwise,
we're not going to bother caching these things.
Send back a thumbnail saying, you're offline,
you can't see this, click Try Loading It Again,
or something like that.
And you can also have user-defined caching.
So if you're browsing blog articles,
for example, and maybe they have a little button that
says Cache This to Read Later.
So next up, we have messaging, push notifications,
So these are notifications that appear on your device
because something happened on a remote server,
some trigger that completely outside the application.
So here we have an example of this.
This demo was created by Monica, who's actually speaking later.
So here those are for people who want to receive notifications
about cats and who wouldn't.
So you toggle a button on say, I would
like to receive notifications, you get a little permission
dialogue in Chrome, which is actually important.
We don't allow applications to show notifications
unless you have that permission and that's
why we have this UI element so that the user clicks it
and then they get a permission notification,
permission dialogue, because then there's
context for that decision.
The user knows why they're having
to click that button to say there were no notifications.
Later on someone comes along and clicks the Send Cats
button and then later notification
arrives and this could happen while Chrome
is completely closed and it could happen a long time after.
And you get a notification and you click it and in this case,
you get a picture of a cat, which is perfect.
Now, how did we achieve this magic?
There's an element for that, obviously.
Platinum push messaging.
As well as sending cats, you could use it
for more serious things, breaking news, chat messages,
new email, that sort of thing, anything
you get a notification for on your phone already.
Platinum push messaging allows you
to do the configuration of all this right in your application.
The server side here is more complicated
and I'm going to just gloss over it and pretend it isn't there,
but for anyone who has implemented push messaging
on Android, the setup for dealing with Chrome
is exactly the same as using Google Cloud
Messaging on Android.
We have a bit of client configuration at the moment
and we hope this will go away in the future,
but right now you need a web app manifest file
and in there, you need to have at least this GCM sender
ID, which you get from the Google Developers Console.
Again, kind of going to gloss over that here.
So here's the actual element.
So here we've just defined statically
what those notifications are going to look like.
So now we've got a title, a body, an image to show,
and a URL to go to when we click.
You can actually set all sorts of other things
on this notification, like even the pattern of vibration
that the device should use when the notification is shown,
which is pretty cool.
But it's a bit boring to have the same message every time,
so instead we have this configuration option,
this message URL.
This URL will be fetched when it's
about to send pop-up notification
and that will instead have a bit of JSON that describes
what the notification should look like,
has all the same options.
And this allows you to dynamically make
those notifications based on whatever data our server
has at the time.
Here I've got a simple URL.
It's just .json, but obviously, you could put in query
parameters or something like that,
that are specific to the current user so that you can get
message details that way.
There is actually in the future, you'll
be able to just have the element with no configuration
because you'll be able to send a body with the push
notification, but that isn't actually implemented yet.
And then I say, you don't want to actually start subscribing
for push notifications without asking the user,
so a couple of things to do there.
I've written this code to fit in ES6 style as you can see.
So we get a reference to the element
and then we hook up the toggle button
to a little function that just says if you just enabled it,
run the enable method and if you've disabled
it, run the disable method.
And then finally when the subscription information
changes, we get an event and we can send that subscription
information up to the server which will then know
how to send messages to you.
So a final thing in our whistle stop talk features
is device access.
This one's a bit more experimental.
It's actually not even only in Chrome,
it's only on Chrome OS in the moment
and it's behind a flag in Canary,
but this one's a bit more interesting,
so I wanted to give you a sneak preview.
So Web Bluetooth is the API behind this
and it allows you to connect to nearby Bluetooth Low Energy
devices, also sometimes called Bluetooth Smart.
And while this is only an experimental API,
thanks to my colleague Francois in Paris,
there's an element for that already, the platinum
This is, again, pretty simple.
You create a device element, pattern
Bluetooth device element.
You give out services filters.
It just says, I want to connect to some device that
is advertising these services.
So here we're just looking for something
that advertises heart rate.
And then inside that we configure it and say we'd
like to know a particular characteristic
of those devices.
So we say the service is the heart rate service
characteristic, body sensor location which,
I believe is wear on your body to wearing the sensor.
And then we hook up the value of that characteristic just using
normal attribute binding.
So we can just take that data and put it somewhere else
in this case, in a span.
Now, these names for the services
and the characteristic, heart rate, body sensor location,
they look pretty nice.
Unfortunately, not every device has the services
and the characteristics with nice names,
so you may have a UUID, a long string of hexadecimal digits,
but you can probably find those in the documentation
for whatever device you're connecting to.
And then similar to the notifications,
you don't want to actually pop up the dialog that says, hey,
I'd like you to choose a device to connect
to unless the user is trying to do that.
So you get a reference to the device element
and then you call request, say that you'd
like to actually talk to it, and then when you want to read,
because Bluetooth Low Energy is usually for passive devices,
the values aren't screened to you,
so you have to call read to make that property update.
But you could do that in a set timeout or something like that
or whenever a button is clicked.
Bluetooth Low Energy does have the concept of notifications,
which will mean that you can get an event when
the values change.
That isn't actually implemented yet in the Bluetooth API,
so it's not implemented in the element either.
Not all BLE devices are passive though
and there was a call demo produced by a Googler
with a Bluetooth API and I justed wanted
to show you a little bit.
So what he did was, he got this grumpy cat toy
and he attached some helium balloons to it
so that it would fly and then he put a little Bluetooth chip
inside, a little Bluetooth module,
and stuck a rotter in its backside.
And then with this little control panel,
he then just made it fly around his apartment.
I apologize for the quality.
It's not as smooth up there as I hoped,
but let's just appreciate that for a moment.
So that was a whistle stop tour of new features coming,
thanks to Paula.
Thank you very much.
You can learn more about the platinum elements at this link
here and there is actually a web Bluetooth code lab
available in the code lab area.
And I believe we have some Chromebooks up there if you
want to try it out.
So thank you very much.
How To Set Pushwoosh Cordova For Android Platform with Ionic Framework
How To Set push.eu/en» rel=»nofollow» >Pushwoosh Cordova For Android Platform with Ionic Framework
Here the steps :
How To Set push.eu/en» rel=»nofollow» >Pushwoosh Cordova For Android Platform with Ionic Framework
1. go to pushwoosh.com, create your account and login
2.Create new app
3.Configure Android Setting in pushwoosh
4.You will need API key from google project, create it one..
5.go to 6.create new project
7.copy your project number
8.activate GCM (google cloud messaging) API
9.Create and copy your credentials : (API KEY,SERVER KEY)
10.COPY your api key into pushwoosh, choose framework = cordova
11. Nice.. next, go to pushwoosh documentation
12.Choose Cordova (phonegap)
13.Create Your Ionic App
14.install pushwoosh plugin to ionic
15.add pushwoosh origin to your config.xml
16.Add pushwoosh script to your index.html
17.Change Google Project Number And pushwoosh app id
18.add initpush.eu/en» rel=»nofollow» >Pushwoosh(); to your app.js
19.you’re good to go, now add platform android and install to real device (it won’t work on browser)
-.I capture the screen on my device using Droidtoscreen
20.App installed, now check your pushwoosh
21.My device has registered on pushwoosh
22.Close the app on device, try to send push message
23.Yes .. I got a message 🙂
visit us at
6 Ideas for Keeping Viewers Engaged with Text Messaging
Over on my family's vlogging channel,
we have been using mass text messaging
to really engage our audience and stay in front of them.
And today I want to share with you guys
six ideas for how you can leverage mass text messaging
to really keep your audience engaged, as well
as three tips for how you can do that most effectively.
That's coming up.
My name is Tim Schmoyer, and welcome to Video Creators,
the channel that is all about helping you
guys grow your YouTube audiences so you can spread
a message that changes lives.
And what better way to spread a message that changes lives
and grow your channels other than by staying in front
of those people who said they want content from you,
but doing that outside of YouTube,
with something like text messaging.
Now I know that YouTube mobile apps have
push notifications built in.
But depending on what research you
look at, somewhere between 60% and 82% of people
just automatically disable push notifications
on their phone across the board– except for text
messaging and phone calls.
Now I'm not about to make a phone call to everybody.
But I am growing a text messaging list simply
by providing a link for people to do that, which I'll
do in the description of this video,
or by simply encouraging viewers to text
the word SCHMOVIES to 43506.
And that will just add people on to my text messaging list
and let me broadcast things and share
things with them that way.
And there are six different ideas
of how I think this could be really valuable and beneficial
to you as a YouTube creator.
The first way is the way that I'm primarily using it,
and that is to announce upcoming live streams.
About 30 minutes, 15 minutes, before my family goes
to live on our YouTube channel, which
we do about one or two times a week,
I will just send a mass text message saying,
hey, we're going live on Schmovies in 15 minutes.
Come join us.
We're doing this, that, and the other thing.
And then I'll just add the YouTube link
at the bottom to that video where we'll be live,
and then just broadcast that out to everyone
on the text messaging list.
That way, they have a little bit of a heads
up and can kind of finish up whatever they're doing,
and then tap on that link and come join us.
Number two, of course you could also
use a mass text messaging list to send out
notifications of new videos that you're publishing.
Maybe that's a separate list from your live streaming list
or whatever the case may be that works best for you
and your audience.
Number three, you can use it to announce meet up locations just
on the fly.
Now I think this is going to be really important for places
like at VidCon as a creator.
And you're not really sure what your schedule is going to be,
but you know you want to hang out with your audience.
Well you can tell them, hey, text certain key word to 43506
and have them join the text messaging list.
And then whenever you're available,
you can say, hey, I'm going to go have
lunch at such and such place.
Everyone come meet me.
Broadcast that out to everybody and they can all come and find
It's different than just doing it on Twitter
or posting on Facebook or something,
where you kind of rely on your viewers
to actually be on that platform at that time
in order to get your message.
This is a way you can kind of interrupt whatever they're
doing and make their phone vibrate in their pocket
so they take it out and see what you have to say to them.
And that kind of goes along also with number four.
A real huge tremendous value of mass text messaging, at least
using the service I use at techsignal.com–
not sponsored or anything.
It's just who I use, and I think you guys would
them– is that your audience can also send replies back.
And this is a great way to get immediate instant feedback.
Number five– and this is one that I personally experience.
When I am speaking at conventions and conferences
and things, I'm on stage presenting,
it's really hard for me to get people
to take out their phones, open the YouTube app
or download it if they haven't already, find my channel,
It takes a lot of work.
But one of the cool things that I
like about the service I use at techsignal.com
is that I can set up an auto responder to automatically send
them a text message back after they text in like, SCHMOVIES
to 43506 or whatever, and the autoresponder message
can have anything in it that I like.
So it makes it really easy for me
to know– like if I'm speaking, I say, hey, guys.
You want to learn more about my channel?
Just text this keyword to 43506 and you'll get a message back
that has the subscription link right there
or the Facebook link or whatever information you happen to want
to give to those people.
And the times I have done this on stage in front of a crowd,
I have literally– I can see visually
how many people pull out their phone and text
the number to get the link as opposed
to going through all the steps and trying to find my channel
and figuring out how to subscribe
and all that kind of stuff.
And I did number six– if you are running a Patreon page
or campaign, I think it makes a lot of sense for you
to integrate this into that as a perk reward
level for your patrons.
So maybe they have direct access to text messaging you,
and you can log into techsignal, for example,
at your convenience and just reply back to those people.
Or maybe this is a secret VIP list
where you're sending special rewards
or special announcements or something like that
just to people who are paying at a certain perk level
to be on this text messaging list for something
that you provide to them.
I think there's a lot of ideas for how you
could use this with Patreon.
But using text messaging is not just like one big bed of roses.
There are some things that I've learned
over time that hopefully will help
you use your text messaging lists more effectively.
And there's three of them.
Number one, you might lose about 45%
of the people who sign up for your text messaging list–
you might lose them immediately if you don't follow up
with an auto response message.
And the reason for that, I found,
is that people need to know very clearly what did I sign up for
and what am I going to get?
You have to set that expectation very
clear from the very beginning.
And I found the best way to do that was with an auto response
Otherwise they sign up, they're like,
I don't know what I just did, and they quickly unsubscribe.
Number two– the best time to send mass text messages
is typically between business hours in whatever time zone
So if your audience is primarily in the United States,
then the best time to do that is probably between noon
and 5:00 PM eastern time.
And number three– this third tip is a little bit more
But what you can actually do is export all those phone numbers
from techsignal and upload those to a Facebook
re-marketing campaign for those numbers,
which is really powerful if you do a lot of brand deals.
There is no other creator that can really compete
on that level and do that.
And if you have no idea what I just said,
then don't even worry about it.
It's not that big of a deal.
I would love to hear from you guys
in the comments below about what ideas would
you have for using a mass text messaging
list with your audience.
And if this is something you want to start thinking through,
as I kind of have, I'm looking forward
to reading all you guys' comments and learning from you.
The rest of you also learn from each other down there below.
If you are looking for a mass text messaging list,
personally, I'm using techsignal.com.
That's just who I use.
And I know a lot of you guys are going
to ask me in the comments.
So I'm just telling you right now.
That's who I'm using.
There's a link to them in the description below this video.
And if this is your first time here at Video Creators,
I would love to have you subscribe.
Every week, we're publishing content to help you
guys as content creators know how you can best
grow your YouTube audience so that, in my opinion,
spread a message that reaches people and changes their lives.
That's ultimately what all this is about.
And hopefully a text messaging list
can help you even do that to a greater scale
and to a deeper degree.
So thanks for hanging out with us, guys.
Subscribe, and I'll see you guys again
next week for more YouTube tips and ideas and news
and everything to help you guys grow your audiences.
See you then.
Devcon: Ran Nachmany Cloud-to-Device Messaging (i.e. Make Push Notifications for Android)
«Cloud-to-Device Messaging (i.e. Make Push Notifications for Android)» by Ran Nachmany
Devcon 21 feb. 2012
Desktop Notifications API
Use the desktop notifications API to display notification messages natively in the browser.
Subscribe to phpacademy and enjoy more free web development tutorials!
Follow us on Twitter!
Push Notifications vs. In-App Messaging: The Difference Explained | Pulsate Academy
Did you know apps that send in-app notifications have up to 3.5 times higher user retention rate in comparison to apps that don’t. In this episode we discuss push.eu/en» rel=»nofollow» >Push Notifications vs. In-App Notifications and in what situations you should use them.
Read the full article:
In this episode you will learn:
1:03 What are the advantages of using in-app?
We describe the advantages of when and in what context to use an in-app notification instead of push.
1:54 What are the use cases of using in-app notifications?
We go through some use case examples of when to use in-app notifications.
2:33 How do you leverage in-app notifications in your app?
We show you how to leverage in-app notification to increase response rates from your campaigns
2:56 What is the optimum frequency for in-app notifications?
We reveal the optimum times and amount of notifications for the best response rates.
If you are using in-app or push notifications in your mobile marketing strategy, we’d love to hear your tips on your success.
If you haven’t already, and want more content on mobile marketing, do subscribe to our YouTube Channel for further great content.
Socialize with Pulsate:
Subscribe To «Pulsate™» Channel HERE: Watch Full Episodes of Pulsate Academy™ HERE: Like Pulsate™ on Facebook HERE: Follow Pulsate™ on Twitter HERE: Connect with Pulsate™ on LinkedIn HERE:
Pulsate is an All-in-One mobile marketing growth stack used by leading mobile marketers to drive sales from their app, increase user engagement and deliver experiences to build brand loyalty.
Pulsate’s Mobile Marketing Growth Stack Include:
See, segment and send content to app users using push notifications, in-app notifications or email.
Customer support teams use Pulsate’s live chat feature to answer questions and respond to user feedback.
Message app users in real-world locations using Geofencing and Beacon signals.
Get real-time insights into customer app behavior, purchasing patterns, app usage and top content.
Pulsate Connect™ (Beta)
Connect, share and stream mobile app data and events between a range of third party platforms and APIs to build smarter omni-channel experiences.
Pulsate Predict™ (Beta)
Predict the likelihood of when certain users will spend, churn or return in your app.