MARC REISEN • DESIGN TEAM LEAD • MOBILE PLATFORM TEAM
Walk before you runDesigning JIRA and Confluence Mobile
Consume Navigate Create Edit
What did our customer activity look like?
we’ll get to these later
Our customers like to read stuff on Confluence…
Feedback module
Consumption and page views make up the majority of our web experience
Search + CommentsPeople need to navigate and browse for their work, and collaborate
Companion App
Have a direct line to your users, make it as easy as possible
We launched!
Quantitative feedback tells you what is happening (or not happening), and qualitative feedback helps you understand why.
“
” Joshua Porter
Quantitative feedback tells you what is happening (or not happening), and qualitative feedback helps you understand why.
“
” Joshua Porter
Heat maps, behavior patterns and MAU and metrics are your friend
Go NativeStart out simple, use native fonts, UI, and common patterns/paradigms
Use Data
Feedback Loop
Heat maps, behavior patterns and MAU and metrics are your friend
Shared ComponentsStart out simple, use native fonts, UI, and common patterns/paradigms
User Data
Create a format to incorporate feedback, user research, labs, testing
Native and shared components
COMMENTING NOTIFICATIONS PLATFORM LIBRARIES
Facebook & Reddit
- threaded
- truncated
- @mentions
Push to Action
- clear legibility
- calls to action
Native Platform Guidelines
- Fonts
- UI
- Familiar to the user
Search
Aggregate of activities in your project or assigned to you
Create an IssueSimple and intuitive way to add issues on mobile on the go
Activity Feed
Browse for issues outside of your context
launched it
the app lacks features. Every month I spend a bit of time on it the hope another month brings it to a level where it can be adopted. Sadly they have a long way to go.
“”
Only just usable
Do you feel comfortable by going live with a non-editable
version of Confluence??‽!! Bravo, Atlassian, Bravo…“
”
Really??
Listen to your users
Keep the context directed to the end user
Keep it simpleUse shared components, whats out there, don't reinvent the wheel
Mobile = Me
Seek to understand, and always ask why…
Listen to your users
Keep the context directed to the end user
Keep it simpleUse shared components, whats out there, don't reinvent the wheel
Mobile = Me
Seek to understand, and always ask why…