by Aditya Sharat (@adityasharat) on Monday, August 8, 2016

Vote on this proposal
Status: Confirmed & Scheduled
View session in schedule
Full talk (40 minutes)

Technical level



Proteus is meant to be a drop-in replacement for Android’s LayoutInflater; but unlike the compiled XML layouts bundled in the APK, Proteus inflates layouts at runtime. This talk will focus on why we built Proteus and how it helped us perform A/B tests and build custom brand pages without any App release.
With Proteus, you can control your Apps layout from the backend (no WebViews). Forget the boilerplate code to findViewById, cast it to a TextView, and then setText(). Proteus has runtime data bindings and formatters. Plugin in your own custom views and attributes and formatters.


  • What are we trying to solve, and why?
  • LayoutInflater, and how it doesn’t work.
  • How Proteus works.
  • Forget findViewById and setText.
  • What you can achieve.
  • There are others out there; kind of


Intermediate knowledge of the Android Framework

  • XML layout and LayoutInflater
  • Building and deploying Android apps.

Speaker bio

Aditya is a Software Development Engineer at Flipkart. He is part of the team which build Proteus. He works on developing libraries, frameworks and tools to promote decoupling, abstraction, code reusability, extensibility, and stability. He is also a full-stack Web Developer specializing in development of high-performance web applications.


  • 3
    [-] Aishwarya Kumar (@aishwaryakumar) 7 months ago

    This looks interesting !

  • 3
    [-] Rahat Khanna (@mappmechanic) 7 months ago

    This looks very promising.

  • 1
    [-] vinayaka naik (@vinanaik) 7 months ago

    Nice work.

  • 1
    [-] Mohammed Shaiban (@shaiban) 4 months ago

    Just one word, Amazing.

Login with Twitter or Google to leave a comment