Loading
please wait ...
Blogs from Coding Club GCT
Ideas Unleashed
In the ever-evolving world of app development, the goal of creating universal applications that function seamlessly across web and mobile platforms is highly coveted. Since React Native was open-sourced, many software developers and companies have leveraged it to utilize the core React functionalities they originally created for their websites. This was possible because of the fact that react is a library and not a framework.
The React Native team advocates for a single codebase solution for Android and iOS. However, what about web development? A glance at the documentation reveals scant information on using React Native for platforms such as web, Windows, Linux, or macOS, unlike its counterpart, Flutter, which supports compilation to all major platforms. Support for web was brought in by the veteran ex-twitter software developer Nicolas Gallagher. Today react-native-web has involved to a compatibility layer between React DOM and React Native. You will be surprised twitter uses few elements from react native for their web but a native implementation for each of their android and ios apps.
Recently, I’ve formed a team with Pavithra VS to build an exciting project: A2A Point. You can find the full project report here. In this post, I will share our team’s design choices in building the web app and mobile apps from a single codebase, adhering as much as possible to the DIY principle. Importantly, we’ve ensured that this approach does not compromise the unique benefits offered by each tech stack, preserving their respective advantages.
This blog would cover three key aspects in this project.
Comment Section
https://github.com/useEffects/a2apoint/issues/2Login to post a comment
Table of contents