Polaris Office
All-in-one Office of 60 Million People Over the World
Improving Android Account Policy
•Duration: Aug 2016 ~ Oct 2016
•Client: Polaris Office ▶︎
•My Role: Problem Solving & UX•UI Design
•All Project Members (13) ▼
The Platform | Android App
The Goal
Examine negative reviews on creating an account and make improvements.
The Outcome
People to use Polaris Office without accounts were allowed, and we also sustained the concept of “Cloud Office”.
The acquisition also improved as the number of new users increased by 1.5 times.
The Process & The Timeline
Why We Started the Project
On Google Play, constantly there were negative reviews on accounts.
“Creating an account is a kind of privacy infringement”
“Why I have to sign up for viewing and editing documents”
have been reported since Polaris Office was released.
Explore & Empathise
We decided to provide the login as a non-mandatory option to solve the problem and increase the influx.
USAGE PATTERNS
•10 percent of users just left the Android app on the login view without access
•80 percent of users chose a document from file manager apps first and then selected Polaris Office
ONE PERSON MULTI-DEVICE
•The number of users who accessed to more than two devices was nearly 35 percent of the total users
•It meant that 65 percent did not log in on other platforms - the web, PC Office and so on.
BENCHMARK
•Double checked that office services which accounts were not necessary like MS, Numbers, and WPS had
few negative reviews on accounts
Envisage
The aim was that "Allow people to choose between using the service without accounts and logging in,
also emphasizing the concept of Cloud Office as service core value."
Maintaining service concepts and android optimization and usability were design principles.
•If users ran the app directly, the app showed the login view with benefits of Cloud Office, providing the “Create Account Later” option.
•When the aim of users was to open a document, the doc was opened right away without login.
•Device storage was used as the default storage, and Google Drive and other clouds were also enabled.
To let users know benefits of Cloud Office naturally, triggers were designed.
•A pdf for introduction of Cloud Office on the recent doc list
•A metaphor and information of connected devices on the navigation drawer
•Cards about advantages of login on the Home view
Polaris office’s business partners did not allow this policy because their users could enjoy a premium service after login.
•Given these requirements, we kept users from using it without an account in specific circumstances
Execute
We developed the scenario with intimidate collaboration.
Quality tests for bug fixes and performance enhancements were implemented.
The Outcome
We succeeded in both quantitative and qualitative sides.
Quantitative Achievement
•The acquisition increased by 1.5 times after the update: People who exited the service owing to the burden of signing up came back to the service.
•The percentage of users who signed in and created accounts did not have change.
Quantitative Achievement
•All project members received a good assessment from a boss: Everything - backup, IA, search, triggers was meticulously designed.
PROJECT MEMBERS
Design
• UI Hyejin Lee & Hazel Park
• GUI
- Concept & Android Jasmine Lim
Development
• Server Paschal Kim, Thomas Jun & Mia Park
• Android Russell Kim, Brandon Lim, Karl Baek & Jace Kim
Quality Assurance
• Android Charlize Han
• iOS Rosa Lee