When a user taps on a push notification, they expect to land on the screen the notification is about. When I started to implement this feature, I found no easy way to do it. Although, I had deep linking figured out, still there was no definitive approach to pass a deep link in push notification and let the link do the magic of taking the user to the intended screen.
React Native Firebase project suggests a simple case of setting
initialRouteName in the
Navigator tag after extracting the route name from the notification’s data object. Refer: https://rnfirebase.io/messaging/notifications#handling-interaction
This is the second and the final part of the two part series. Find part 1 here: https://medium.com/cybermonkey/mastering-over-the-air-updates-in-react-native-with-codepush-part-1-faf241a7f84b
As happy and dandy as we feel after setting up a pipeline that makes majority of app release bypass the app stores, but the happiness does not last long when you want to do a pre-release testing (Alpha Track in app store) or a beta testing with beta participants, or A/B Testing over 20% of all the users. Only if CodePush could do these for us. Well, you are in luck, CodePush can do all this and more. Let’s explore?
The initial days of a new mobile app development is a melting pot of frequently added features and improvement, broken-for-certain-devices releases, bugs slipped from the tired eyes, and an out-of-patience-midnight-oil-burning-DevOps with a dark sense of humor. The only thing you do not want at this point is a third party authority with their impractical review policies guarding the doors of the mobile phones where your broken code is pushing the users to the brink of uninstalling the app and writing a scathing review on the store about how poorly developed the app is, ignoring all the hard work done by…
I hated ReactNative’s YellowBox during development. So, I was eagerly awaiting for the version 0.63.x to switch to. It has much saner LogBox. At CyberMonkey, we try to keep our dependencies updated. We know, it isn’t as easy as just updating the React ecosystem libraries in
package.json. So, let’s get going?
BRANCH YOUR CODE
If you haven’t already, please backup your working code because this process may backfire. I strongly suggest you use a source code management tool like Git or SVN. Assuming, you are using git, let’s make a local branch:
# Creates a branch named rn_upgrade_0_62_2_to_0_63_2 git checkout…
In this final chapter of the three part tutorial, we will discuss some of the advanced features offered by
i18next, these topics will include rendering dynamic strings using features such as interpolation, formatting, setting timezone locale, pluralization, nesting, context, and JSON objects and arrays.
If you want to learn about configuring localization and internationalization with i18next, jump to part 1 of this series here: https://medium.com/cybermonkey/multiple-language-support-in-react-native-part-1-fa6966b62332
If you want to learn about organizing translations for a medium to large application and providing language change control to the users, hop on to part 2 of the series at https://medium.com/cybermonkey/mastering-multiple-language-support-in-react-native-part-2-d33262acc21d
This article runs in three parts. Part one can be accessed here: https://medium.com/cybermonkey/multiple-language-support-in-react-native-part-1-fa6966b62332
If you are looking for the code for part 2, checkout
part_2 branch of the GitHub repo at https://github.com/naishe/rn_multilanguage
In the last part, we have got the basics of multiple language support done. We could set up a project, guess the best possible language, store and retrieve language preference and display content in the language. It sounds like we are done, but for any serious medium to large project, there are a bunch of things you want to do to avoid pulling…
This article runs in three parts. If you are looking for code, please use
part_1 branch of this repo: https://github.com/naishe/rn_multilanguage
The second part can be accessed at https://medium.com/cybermonkey/mastering-multiple-language-support-in-react-native-part-2-d33262acc21d
If you are serving a multilingual audience through your app, it becomes quickly obvious that supporting the languages of the demography will give you an edge over the singular language app. Working on ThatMate’s mobile app that serves sexual and mental health education to children and young adults in India, we came to realize that we will have to support multiple Indian languages along with English sooner…