-
Highlights from Today's #TouchlabShare with @RussHWolf @TouchlabHQ/1257324068455370753
-
Russell launched github.com/russhwolf/multiplatform-settings on April 16, 2018 @RussHWolf/1250914078505291782 #TouchlabShare
-
Was on a project trialing React Native, which was frustrating, but got him thinking about what he wanted in a multiplatform framework. He started paying attention to the space, and even discovered @doppllib [JM: memories...] #TouchlabShare
-
While on another project built with #KotlinMultiplatform, he pulled out the shared preferences logic into a library. Over time, added other platforms #TouchlabShare
-
Last week, he published version 0.6. Read more: @RussHWolf/1254501489223118849 #TouchlabShare
-
Early on, he made a lot of guesses about what developers may want based on his own needs and experience. Feedback came slowly, but pull requests and github issues started to come in. People even started to give feedback on Slack and Twitter. #TouchlabShare
-
For a library, you need to be more general. It's not just your own use cases, but also the use cases of people who want to use it. You also need to keep things more stable. #TouchlabShare
-
Something he'd do differently if starting today, is around Expect/Actual. It's one of the first things you see, so it's a "shiny toy" you want to play with, and it is useful, but it's easy to over use, and he did over use it #TouchlabShare
-
If you want to swap out implementations, e.g. in you test code, it's better to present an interface so the user can provide their own implementation. It also means he can publish an interface to any platform, including ones that aren't implemented yet #TouchlabShare
-
APIs are fairly similar across different platforms WRT settings storage. The more platforms you add, and the more you try to support them, the more differences you noticed. And it is a challenge to find the right balance #TouchlabShare
-
Done. Great job @RussHWolf!