Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Designing Mobile Messaging
Transcript of Designing Mobile Messaging
where do your users interact with your app?
tapping the app icon?
chat bot maybe...
of apps installed will never get launched
of apps started once will never get used again
1. app’s capabilities vs user’s expectations
2. forced to use the app for a one time action
3. app is not habit forming
getting an app downloaded is easy, but having it used?
head of ux @emarsys
*some apps don't need messaging, but you probably do
is a finite resource
make sure to not overdo
every message should be meaningful
Relevancy comes from content, it should be both have some actual substance and designed in a way that helps digesting it.
The message should be tailored for the user, the information piece created just for her or something based on the her behavior.
The message coming at the right time, maybe at the right place or even on the right channel.
The user is able to do something with the message, the action is effective, the user is able to do what the action called her to do.
Get proactive and give the choice to your users and maybe retain some messaging options for latter.
Twitter's "Popular in your network" email:
: might be, hit or miss
: might be, but doesn't really feels like
: you can interact with the tweets, no indication why you should do that
: not really right time (but might open it in the morning)
: clear opt out button at the end
opened on mobile
click rate (responsive)
* numbers vary a lot by industry
summary of activities
information intended to be kept for latter reference
Easy to make
since very little constraint on content or design. Hard to make it really
, as emails are not timely,
through click through buttons.
subject line: first 25-30 characters matter
responsive is must
limit the length especially for transactional emails
test in mobile clients
don't build on images
highly critical info
time sensitive info
when internet may not be available
is hard due to design constraints, good copy is essential.
think in conversations instead of individual messages.
is possible via time and geo targeting,
is either link or physical interaction.
You don't need an app te send SMS!
SMS costs (way more) money, so you need good plans (especially for multi part messages)
Phone numbers can get recycled
transactional messages that require the user’s action
highly contextual information.
great for reengagement
Few design constraints (like length), but there are enough options for making it
you have tons of info about the user.
is very easy you should have access to most sensors. With built in
easy to start interactions even without entering the app.
Know your platform guidelines, huge differences in mechanism for Android and iOS. For example Android can display images too, you can manipulate icons etc.
Vibrations - for really important info
Using sensors can be very powerful, like not sending stuff when battery is at 5%, or sensing fast movement.
Interviews and field studies rule here, they can uncover new scenarios where messaging will be important.
Do your research.
Design your story.
A journey mapping or a story mapping exercise helps visualizing their story and uncover further message touch points.
Have a copywriting guide.
Have guidelines for writing words to have a consistent tone of voice. Product stance, your app's personality helps in defining this.
Clicking the message should bring the user straight to that exact point in the app where the feature is.
Never use placeholder text and dummy data if you have real data available during design. Even if the users don’t input any data about themselves, there are still many things you can build on, like app usage patterns, date and time, other sensors.
Design with data.
Automation can help to implement complex strategies on when and what messages should be sent.
Context, context, context.
Research should uncover lots of interesting scenarios, but a source of true delight is when you can anticipate and resolve the user’s anxiety with something happening in their own context.
Measure open rates, actions taken and unsubscribes (or even uninstall rate). But don't focus on the vanity metrics alone, look at the overall effect of messages and the final outcome.
Measure the effects.
Make sure your first message is great, as it will set the expectations for the rest of your messages (and help avoid opt-outs).
First impressions count.
ads, app store desc, ...
in app onboarding, push, welcome email, newsletters, ...
proactive messaging, push, transactional messages, newsletters, ...
rating prompts, promotions, sharing, ...
don't like getting spammed
too many notifications
When going for metrics, people tend to be viewed as numbers on a dashboard.
It is possible to design for optimizing this (dark patterns), but it doesn't result in long term engagement and not too nice either.
engagement happens here
- getting swiped
don't like being interrupted
metrics vs people
choose your channels