Pushing Dynamic Features Your Users Want, As Quick As They Want Them
Many successful Android apps offer multiple features and components that work together to provide a great user experience. Although you want all prospective users to have the ability to install your app, this may not be possible due to limitations in storage and network connection, especially in emerging markets. What if you can deliver new features selectively post-installation, reducing the initial app size, and allowing you to target a wider audience? How did Kotlin enhance your reliability and quick prototyping before shipping a brand new dynamic feature? Now that Kotlin is the first language on the Android platform, you certainly know this was the right choice at the time.
What will the audience learn from this talk? The good, the bad and lessons learnt we had along the way when building our first Dynamic Feature at Twitter for Android. Technical Design decisions we made, some architecture and implementation details (code samples in Kotlin language) and thinking in behind them. What is a dynamic feature? Why did we choose to make it? How did we make it? What difficulties did we have? What are the next steps?
Does it feature code examples and/or live coding? It does have code examples but not live coding.
Prerequisite attendee experience level: Level 200 Description Intermediate material. Assumes 100-level knowledge and provides specific details about the topic.
Code examples will be guided and explained, diagrams and workflows would give a better understanding of the content and wider context will be given with real use cases. No necessary to be an expert, but some coding experience in a language like Java / Swift or Kotlin would be good to have to understand the code snippets.