Versioning is a critical component of your app upgrade & maintenance strategy.

If you’re a developer with a certain level experience you know that it’s not a good idea to keep constants like API endpoints, Secret keys hard coded around the codebase.
To address this what we normally do is to keep an .env file with configurations as key value pairs & access them universally at any point in the codebase.

What if we can do the same thing for versioning a react native application?


In this article we’ll be discussing on building a robust stylesheet guideline for react native. This guideline is built with the aid of theming provided by react native elements along with Stylesheet API in react native. However at the end of this article you will see that its not just limited to react native elements at all. Along with this we’ll see how some blockers such as code separation, module resolution issues in compilation, type safety… etc. were resolved as well.

Why even bother with theming ? 🤔

Features like theming or even internationalization are common to be found in majority of the applications found in the…

Pasindu Dilshan Gunathilake

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store