What is your background as a developer, and how did you end up with SAP?
People often think that I’m a developer, but the truth is that I’m a UX designer with solid coding skills. I started designing websites back in 1999, shortly after completing my studies in Industrial Design and discovered a passion for code very quickly. In 2007, after a few years working as a freelance web designer, I had the opportunity to join Dailymotion, a French video platform who at the time was competing directly with YouTube.
When your direct competitor belongs to Google, you have to be good. This is where, surrounded by really great developers, I learned to design for a large scale website and discovered the importance of User Experience design. Being the Creative Director of the worlds second largest video platform was an amazing experience but I left my position in 2010 to join SAP’s Visual Design team based in Paris to start something totally different.
Has your experience at SAP (a huge multinational company with a huge software suite) informed your thinking on mobile applications? If so, how?
I was lucky enough to work on Dailymotion’s mobile applications very early and sharpened my design skills on iOS and Android when those platforms were released. I joined SAP with a good knowledge of mobile but I had the opportunity to learn a lot with SAP's Mobile UX team based in Palo Alto. If you have a look at Apple’s AppStore you will see that SAP has become one of the largest mobile apps editor in the world and is for sure the number one when it comes to apps for enterprises.
Your talk is about porting iOS apps to Android. Do you think typical app developers should start with iOS and port to Android or work on both simultaneously? Does it matter?
The reality is that when you create an app for mobile, the first choice always goes to iOS. This is even more true when it comes to professional apps. But today Android is the number one platform in the world and it can’t be ignored anymore. This is the reason why most of the Android apps on the market have been ported from an iOS app. The result is that you will often see Android apps that look like iOS and this is becoming a real problem for the Android user experience.
What should audience members expect to learn from your session that they may not have known?
The Android Design Team released their guidelines less than a year ago; the platform now has a very strong visual identity and its own interaction patterns. Replicating your iOS app design to Android is not acceptable anymore, but adapting it is a lot easier than what you think. We will see how to translate design patterns from iOS to Android and have a detailed look to the Android Visual Identity to understand what you will need to change to fulfill Android’s users expectations.