Apr 2015
13 Mon
14 Tue
15 Wed
16 Thu 09:30 AM – 12:15 AM IST
17 Fri 09:30 AM – 12:00 AM IST
18 Sat 12:00 AM – 12:15 AM IST
19 Sun
Designing and serving content for multiple mobile and web platforms is hard. Come hear about some of the problems we faced, as Myntra migrated from serving fashion content on one platform to five platforms. How step by step, layouts and templates were pulled out from the app and into the server, to be freely changed without an app update.
Long ago, a website had to be tweaked to work correctly in individual browsers and operating systems. Buttons, sliders and drop-down menus appeared differently on different operating systems. The web was the glue that defined their configuration, and the browser rendered these individual interface components for you. Soon CSS followed and you were able to specify styling attributes for these components.
With the mobile age, we are back to square one. Everyone uses the ‘web’, not via the browser but via apps in the form of ‘HTTP’. Unfortunately, compiled apps have to be updated everytime something changes. iOS, Android, Windows Phone SDKs bring their own implementations of these interface elements and it is time for us to bring the remote configurability of the browser to these native elements.
Here are the things we already know:
Here are the things we want:
We have attempted solutions to the first three things, and would like to share them with you. (Meanwhile feel free to attempt the fourth.) It’s like Photoshop for building app content in the age of mobile platforms. Upvote the proposal and come hear the full story.
Understanding of the web and native apps in general.
Working as a frontend engineer at Myntra since 2013, till unsolved problems in frontend layout tools for iOS and Android forced us to dabble in engineering some backend systems.
Hosted by
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}