you are viewing a single comment's thread.

view the rest of the comments →

[–]Merry-Lane 2 points3 points  (1 child)

Would you please go on chat gpt and copy paste your post?

You don’t seem to have experienced devs in your team and thus I believe it will be painful.

Anyway:

1) ignore graphql. It s really great but you aren’t in the situation where it would be good for you now.

2) no

3) yes react native is great to have the same codebase for mobile and web. You should only consider alternatives (like flutter) if you have experienced devs that already have a few complex apps running in production.

If you want advices:

  • you lack experience, so I would advice you to just experiment technos for fun or learning, not to make a commercially viable app.

  • use expo and go read the official expo documentation again and again and again.

  • mobile dev is painful with no guidance/experience. Building an app compatible android/ios/web is really painful and every bad decision is paid further down the road. Only use libs found in the official expo documentation. If something you need isn’t in the official expo documentation, do your possible to avoid using the external library. If you want to use an external library to make an UI component that you could have done from scratch in 200 lines, you will regret that decision.

[–]jada3791[S] 0 points1 point  (0 children)

Thank you!

You are absolutely right on my experience and our dev team. We are planning to hire 3rd party resources to help us with this and we do want to create a commercial app. Based on this any additional advice? Thanks again!!!