React VS react-native

React.js

See the releases section of the React codebase, and see how many reactions each release note has!

You know you can just check before making these claims?

> In fact, for years, react didn't even tell in the doc you could use it without a transpiler so people had to learn a whole build chain before even getting to the hello world.

React's original documentation site from June of 2013 (when React was first introduced):

https://web.archive.org/web/20130607085014/http://facebook.g...

Feel free to click around that original documentation site.

Here's the README.md from the commit at the same time:

https://github.com/facebook/react/tree/a41aa76ef36471ba07b29...

> You'll notice that we used an XML-like syntax; we call it JSX. JSX is not required to use React, but it makes code more readable, and writing it feels like writing HTML. A simple transform is included with React that allows converting JSX into native JavaScript for browsers to digest.

At this point I would kindly ask you to go away.

For further insights, refer to the React documentation to learn more about the library.

To get started, let's quickly create a sample React app that has a build configured to export a static site. Even if you have a project in mind to deploy, I recommend going through the motions with a simple sample site, as you may run into implementation specific issues with your project & if you've never gone through the motions, it can be hard to determine whether you made a mistake in the deployment processes or if there are implementation specific issues you're facing.

In the company I work at, our frontend codebase consists of couple of thousands files. The framework is React 16 and the bundler used was webpack 4.

Enter React, React Native, and Expo. By unifying our development stack, we streamlined our workflow considerably. Yet, one crucial piece was missing: a comprehensive library for essential tasks like icons and components. As we delved further into our development journey, we realized there were more gaps to fill, including robust boilerplates and other essential necessities.

React doc: https://react.dev/

When taking about cross-platform flexibility, Svelte also has Svelte Native like the way React has React Native for mobile app development.

1. React Native: Transition into Mobile Development with React Native, allowing you to reuse JavaScript knowledge. The official React Native documentation is a good starting point.

react-native

Enter React, React Native, and Expo. By unifying our development stack, we streamlined our workflow considerably. Yet, one crucial piece was missing: a comprehensive library for essential tasks like icons and components. As we delved further into our development journey, we realized there were more gaps to fill, including robust boilerplates and other essential necessities.

The best option is probably Flutter right now: https://flutter.dev/

If you don't mind writing the UI native, sharing only business logic code, Kotlin is an option: https://kotlinlang.org/docs/multiplatform.html#kotlin-multip...

Kotlin also can do the UI if you use Compose: https://www.jetbrains.com/lp/compose-multiplatform/ ... however, iOS support is still in alpha, and Web is "experimental". If you're not willing to cope with that (expect to have to change your code as they develop the framework) then Flutter is the way as it's pretty stable already on all platforms.

If you already know Typescript and React, you may also consider React Native: https://reactnative.dev/

On my last post I talked about how I recently started learning react native to build an idea I've had for a mobile app, this time around I want to dive a little deeper into react native.

I know, real original 🙄, but I had to as this is my inaugural post on Dev.to! I've been toying with the idea of writing a blog for some time now, and figured since I'm starting a new project, this is the best time for it. I've been somewhat familiar with React.js for a while now and wanted to make the jump over to React Native to capitalize on an idea I've had for a few years. I'll be blogging about the progress on my app and figured this is the best spot for it.

There was always a tiny sparkle in me telling me that I want to develop mobile apps but I never pursued it. It always felt a bit complicated for me to learn development processes in a completely different industry. I did try developing mobile apps using React Native but it never felt right for me. Also, I already tried to write some Kotlin code and so far I like it, but the whole Android ecosystem is still pretty new to me and I feel there will be a lot to learn. Nevertheless, I will try to learn it in parallel with Elixir but Elixir will be my primary goal, and Kotlin / Android will go along depending on how much time I will have.

This is a modified version of the file from the react native cli template

Recently, there has been a notable shift in mobile application development practices. Rather than creating separate applications for each native platform, many developers are opting for hybrid mobile frameworks like React Native.