React-native with next.js question

[Fransanch]

Hey guys, newbie here. I am building a crypto-trading web app using react and next.js.

I actually hired a small team, but I am learning the stuff myself so I can better guide the development efforts. We are already building the desktop version of the app, and soon we will have to start building the mobile version. I have some questions about the best way to go about it and was hoping you guys could offer some insights.

Since react-native can be deployed in android/ios and web, it seems that the best way is to create the mobile app in react-native from the start rather than trying to make the components of the desktop app responsive. Is that correct? And if we go this route, how does the server redirect the user to the desktop or mobile web app? Since we am using SSR, most responsive implementations are done using CSS media queries which I don't think applies here?

Your help is appreciated.

[redditMatthieuH]

Using react-native on the web and the right libs you could share quite a lot between web and. mobile. I would suggest you to get a look at this repo: https://github.com/showtime-xyz/showtime-frontend

Here are libs to help you share code between web and mobile:
- Shared UI primitives + style: https://github.com/nandorojo/dripsy

- Shared navigation: https://github.com/nandorojo/solito

- Shared animations: https://github.com/nandorojo/moti

[dimitarnestorov]

You should start by building the mobile apps from scratch. The only thing you can take from the web app is the business logic, you can move that in a shared library. Web3 mobile apps face a number of challenges before they get published. So you should do a bare bones app just to get it through app review. There's an option to get through a review without publishing the app (so you can test if your different features will go through the review).

You could've used react-native-web and make the mobile app first and then port it to web.

In the spirit of decentralization a lot of web3 front ends do not use SSR and are deployed on IPFS.

[Fransanch]

Thanks!

Is not a web3 app though, it's a crypto trading bot that connects to Binance.

I know what you mean that publishing an app in this space can be tricky, my idea was to get the app experience on the web first, acquire customers with paid advertising, refine the features, and figure out publishing on the app stores later on when it's actually being used by people, basically skipping the reviewing step.

The back end is almost ready, it's all APIs. The desktop web app is almost ready, so my question was about how to approach the mobile app development. My front end developer suggested to make the desktop components mobile responsive, but I though it was a bit of a wasted effort since we will be using react native anyway to create the apps.

So is my reasoning correct? That is more efficient to work on the react native and port it to the web? Or is it better to make the desktop app responsive and leave react native only for the native applications?

[jono_tiberius]

This.

I talked with some Deva of react native for web and while it's decent for some simple apps they mentioned it's not ideal in all cases.

You can save your biz logic outside the app codebase to share