The main cross-platform frameworks have come a long way. Flutter, React Native, and Expo are not toys anymore. For most common native APIs, there is already at least one wrapper, plugin, config option, or known path: location, notifications, camera, permissions, storage, analytics, payments, deep links, crash reporting. The normal native bridge story is mostly solved…. Continue reading
Implementing Expo apps can sometimes feel boring. Yet another view, yet another component, yet another Zustand store. Not often do you get a chance to venture out from the safe and comfortable Expo stack. But sometimes, you get the opportunity to do something you never thought would happen: embed a full native view into an… Continue reading
One of the tedious chores with mobile apps are the screenshots for Play Store and AppStore, especially because this is the only way how you can showcase the app to potential uses. Also as app grew, it may get even more time consuming since the number of screenshots, supported languages, pre-configurations and features increases over… Continue reading
Lets talk redux for a brief moment. As you may know there are three main ingredients in redux: action, reducer, store. From the first look this kinda makes sense. You have your store with is actually your app current state. Reducers are pure functions, as such they are disconnected form everything, just take current state,… Continue reading
This is something that I have found myself doing really often in my Flutter code base lately. If you are you are familiar with react-redux patterns on the web (or react-native) this would be probably obvious for you. Most of my Dart files (with Flutter widgets) right now have at least two widgets. First is… Continue reading