What's changed #2: App update

Apps > Binary > Upload New 

Changed: App upgrade procedure 

+ update : 2013-09-25

What we wanted to change in the first place was our app upgrade procedure. Some developers told us that it's not so easy to submit a new version of application and replace previous one, and some others told that they already became familiar with the old system.

So we decided to support both type of developers at the same time, by preserving current procedure and adding up a new way of upgrading apps.

  

This is what we've done: 

AS-is "File replace" was upgrade actually 1. Confusing menu name  2. Not so good UI/UX 3. Version isn't associated with Manifest

To-Be Stop Replacements! Just update! 1. Just click update button on the list! 2. Totally easy to use, right? 3. Add various kind of file information      just for APK

Problem with the old way

<기존 UI에서 발생한 업데이트 문제 해결 방법>

As you can see in the video above, there were some developers - especially non-Korean - who submitted more than one application, while thinking they're upgrading their existing one. We have got tons of mails why we designed upgrade procedure so confused.

Why not! we kept both!

I really struggle to solve this problem and to make user familiar with provious system without any problems by finding UX improvement. As a result, I drastically modified UI/UX of website that can keep old & new operations for APK update.

1. New way: Tell us the uploaded binary is an update or not

- Upload New Binary > Update Existing Binary > Select target > Update

- Existing information like filename, last update date, Manifest can be seen. 

- Click update button if you want to move on.

 

2. (Improved) Old way: Update binary file 

- Developers can directly update their existing binary file.. 

3. Check the Screencast 

- In this screencast, we're showing these two ways to update an app. Plese check this out!