The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". This cookie is set by GDPR Cookie Consent plugin. These cookies ensure basic functionalities and security features of the website, anonymously.
Necessary cookies are absolutely essential for the website to function properly. This led us to build a lightweight Hendrix mobile SDK - a great candidate for Kotlin Multiplatform as it requires significant business logic and is entirely platform agnostic. Poor network connectivity coupled with frequently changing configuration values in response to user activity means that on-device rule evaluation is preferable to server-side evaluation. For our use-case, we’re configuring the availability of production, version, and region specific app feature sets. These expressions are evaluated in the current app session context, and can access data such as A/B test assignments, locality, device attributes, etc. Our first exploration with code sharing involves the implementation of a mobile SDK for our internal experience management tool, Hendrix.Īt its core, Hendrix is a simple interpreted language that expresses how configuration values should be computed. Decoupling the code that manages these configurations from the apps themselves helps to reduce complexity as the apps grow. This translates to a large number of app configurations to toggle feature availability and optimize the in-app experience for each production. Now we’re taking this one step further by using Kotlin Multiplatform to write platform agnostic business logic once in Kotlin and compiling to a Kotlin library for Android and a native Universal Framework for iOS via Kotlin/Native.Īs noted earlier, our user needs vary significantly from one production to the next. The need for fast product delivery led us to experiment with a multiplatform architecture.
The high likelihood of unreliable network connectivity led us to lean into mobile solutions for robust client side persistence and offline support. For these reasons, as a small engineering team, we’ve found that optimizing for reliability and speed of product delivery is required for us to serve our evolving customers’ needs successfully. The nature of the work means we’re developing write-heavy software, in a distributed environment, on devices where less than ⅓ of our users have very reliable connectivity whilst on set, and with a limited margin for error.
The world of physical production is fast-paced, and needs vary significantly between the country, region, and even from one production to the next. Over the last few years Netflix has been developing a mobile app called Prodicle to innovate in the physical production of TV shows and movies.
0 kommentar(er)
