JSFoo 2019

On component architecture, front-end engineering and Developer Experience (DX)

Building for developer experience

Submitted by Rahul Kadyan (@znck) via Zainab Bawa (@zainabbawa) on Sep 9, 2019

Section: Full talk (40 mins) Technical level: Intermediate Status: Confirmed & Scheduled


At Myntra, we have hundreds of micro applications built over a few years by a continuously changing team. Different people brought different ideas, and these applications became an amalgam of different design processes, themes, libraries, and tools with lack of any governing principles. These differences and no governance led to multiple forks in design and experience. Now, we have a solution which unifies the forks, makes it easier to deliver consistent user experience and much more.


In this talk, I share the problems we faced:
- In maintaining a component library.
- In supporting hundreds of applications.
- In communicating design decisions.

And how we ended up building tools for fixing broken developer experience, which in turn addressed the issues of user experience inconsistencies.

In short, this is a story of re-making of a design system until it made sense to everyone.



Speaker bio

Rahul Kadyan is Vue Core Team Member, and senior software engineer at Myntra.





  • Praveen Puglia 8 months ago

    My comments from the first call

    • How do you deal with different frameworks / teams or that wasn’t the case in your migration.
    • What’s the afterstory? I would love to see some stats!
    • Can you please mention all the public tools that you use and for the purpose you used it?
    • I would love to know the goals upfront. Because your choices would have depended on a particular set of goals. So when mentioning the problems, I would also love to see the goals side by side. A one to one mapping would be amazing!
    • If you did gradual changes in a project, say migrated parts of an app then how did you manage the old and new part?
    • Did it do anything on the Designer productivity front?
  • Zainab Bawa (@zainabbawa) Proposer Crew 8 months ago

    Thank you for the run-through of your presentation, Rahul. Here is the feedback from yesterday’s review:

    1. What were the objectives of undertaking this exercise? Show before-after situation. Do you have quantifiable numbers? Show the audience quantifiable changes each time you made a change. How did developer productivity improve?
    2. The way to sell your approach is to show metrics.
    3. How did you convince the stakeholders on the what and why to go through this? (Rahul’s response was that this started as a team initiative. When benefits were visible, manager was convinced. A new team was created called UI platform team. Software development cycle showed visible results. Two-three products were shipped. Then there was company-wide adoption.)
    4. Trade-offs of this approach – what were the time restrictions? (Rahul mentioned that collective knowledge had to be built. Please leave and join teams.)
    5. Why did you choose SAAS? (Because of stability, according to Rahul.)
    6. How do you deal with different frameworks?
    7. What is the after-story?
    8. Point out all the public tools you have used and the purpose of each.
    9. How did you think of problems in relation to end goals? So how did you approach the problem with the end goals in mind?
    10. If you did a gradual change, how did you handle old and new code?
    11. Did you do anything which increased the productivity of designers? Explain.
    12. Refer to Nadia Makarevich’s slides and talk since your story of DX has some resonance in the JIRA story which Nadia shares.

Login to leave a comment