I agree with John. For the most part, Flutter has been easier to maintain as time goes on when comparing to react native. And in the landscape, the people at Flutter appears to be very active with the framework, a lot of things cooking. Flutter web is very new, but it'll only get better, more stable.

For the most part, Dart/Flutter is a great choice for cross-platform application development. The platform is developed by Google, and will be around for a long time. Unless you need to do very low level stuff, like bluetooth tethering or 3D drawing, flutter should be able to handle anything you need it to.

We also had the same discussion, but ended with Flutter cause of it's great community support & great set of packages. Also achieving calling native feature is super smooth. And Flutter support Web as well while React Native don't. Learning curve is also a great point to choose flutter all doc's official videos are super rich to help you out.

We have experience with React Native, Flutter or Xamarin, the lion share of the native cross-platform tools used. They all allow you to create very good user experiences. You can check their reddit pages to see the beautiful designs people recreate. I highly recommend using cross platform tools vs native if your app has generic functionality that doesn't use advanced functionality of the app like VR/AR. So, for something like a dating app without those features, you would probably be better off with cross platform native instead of single platform native (swift/kotlin). If budget is low, a lot of companies have success just using Expo (a framework on top of React Native). It limits you further, but it's the easiest and most affordable to find developers with. Eventually you might decide to move away from it, but at that time ou ll have a lot more money and react native will be an easy tech to move towards.

Xamarin is the oldest of the cross platform native tools and so there's a lot more documentation and supporting libraries.

Flutter is super fast & fluid, and since it uses pixels(skia), it's even more performant than all the other technologies including native single platform. But it doesn't come with the amazing libraries that Xamarin and React Native is able to leverage

As the previous commentor said, Next.js or React Native + Expo may be a better option. There's also the options of AssemblyScript + React/Next.js, or NativeScript and Ionic, both of which give you mature ecosystems of tools and close-to-native experiences. Flutter, you're likely to have the same experiences you had with Swift and Kotlin. Flutter requires higher separation of concerns between platforms, doesn't have nearly the third-party support of any of the other options, and is fairly large in binary size. Still, it's a growing system and in the future it may actually outcompete the other options when it has a large enough ecosystem.

Framework like Flutter or React Native can never replace native technologies, Both platform launches their features onto their official framework and Flutter or React Native adopt these new feature via their community support that so you might need to wait or you can write on your own. Also performance is a great factor if your are more focused on performance then it's always advised to go with native on. One of the emerging technology is Kotlin Multiplatform you can try this one if you are building app for both platform. KMM can help you to put all you business logic at single place and can construct UI on the native language.

Still if you wanna move toward the Flutter or React Native my advice is to go with Flutter cause of it's increasing community support & industry choice.

If your team has a strong background in Python and you want to release some prototype soon, you could try Python and Kivy. Kivy is an open-source, cross-platform Python framework for rapid development of mobile GUIs. It supports both iOS and Android. I have passed a similar situation recently: to start a mobile app with no background in mobile development. Kivy saved me a lot of time. I could develop a prototype and release it faster than I thoght.

To be honest , You need to think these points :

• Developer Experience

• Tooling

• Maintainability

My vote for now is going with React Native with Expo , using Typescript...

With this stack You could follow some patterns and principle that the Java and python programmers are familiar with.

Typescript is a javascript Superset that you can follow Procedural , Functional and OOP approaches and an easy learning curve.

With Expo you need to concern only with the shared layer (Typescript) and the Native ones will be expo responsibility.

Please check Expo.com and try to get started using typescript.

Good performance and with EAS (paid plan) you can create a full CI CD pipeline for your app connected to the stores(Apple and Android).

If you already know how to build web apps, give Capacitor a try. You can think of it like "electron for mobile" in that you can build a web app but access native functionality. Pair it with Ionic if you want a UI kit that is optimized for mobile, or build your own UI from scratch.

A bonus to Capacitor is your app will run without modification on the web as a PWA, iOS, Android, and more.

Other tools have very slow performance. They are usually selected because someone on the team likes Angular, but your customers won't care what framework you're using. They'll just know the app is slow.

I think you should go with Flutter any day because there is a large variety of widgets inventory for it which can fasten up the development time to at least roll out a minimal viable product out there. Performance of Flutter Apps are also better than React Native apps. And as an added bonus, if in future you want to add a web interface for the same, you can do it using the existing codebase if written in Flutter (dart).

IMO if you need to build a simple and quick UI for your app, I'd suggest you go for either React Native or Android with Java or Better Yet, Kotlin (It won't take much time for you to get familiar with it if you know Java. See this https://play.kotlinlang.org/koans/overview). For Backend APIs you can use Python with something like Flask

It depends. If you only need it to run on Android, you might be able to develop it faster in Android Studio (Java/Kotlin) with your experience with Java. Kotlin syntax is different than Java, but Android Studio has conversion from Java to Kotlin built-in.

If you need apps for both iOS and Android, or you are willing to be pushed out of your comfort zone and build experience, definitely go with Flutter/Dart. I was able to translate my iOS and Android native skills to Flutter/Dart very quickly. Performance is as good or better than native, and much better than React Native. Development is actually faster than a single platform native app, as well.

If a web app would work, you can use your Python skills to build it quickly with Anvil. They handle hosting and deployment, with built-in database and user authentication. There's a drag-and-drop UI designer. But we're not talking a "no code" solution here. You write all the logic (both server- and client-side) in Python.

I think in the long term Flutter would be your best bet, I work with both flutter and react native daily and I am constantly finding reasons why flutter is better then RN, some general things I've found with flutter are the following:

• User base is growing massively and a lot of companies are switching over to flutter
• Performance is much better than React, both usage and compile times.
• Managing framework updates with Flutter is a breeze and not so great with React.

I have been exploring the Flutter lately it's good but if I am building something which is really huge then I will definitely use React Native for these reasons

1. React Native is used by so many big companies so there are libraries for everything you need.
2. As of now React Native community is bigger and more active than Flutter so if you're stuck anywhere it will be easy to get help or just find a solution from stack overflow.
3. Since you're already working on JS you wouldn't need to learn anything new and you can focus on building your product.

The question you should be asking yourself Do I want to spend my time learning a new framework and then build the product or should I just building the product with the framework I know.

I would definitely go with Flutter. I have been writing native apps in iOS (Objective-C/Swift) and Android (Java/Kotlin) for over 6 years. For public-facing apps, we have generally written and maintained 3 code bases (iOS, Android, Web), so we have tried cross-platform solutions, including Ionic and React Native. React Native was definitely better than Ionic, but still lagged significantly behind native, in terms of performance. Flutter is a game-changer. I have been tasked with writing a public-facing app to help users identify fish species. It is backed with AWS Amplify (AppSync/GraphQL). I was able to write a platform-aware UI, with native-looking elements in less time than it would have taken me to write it natively for a single platform. It looks like with just a few UI and backend tweaks, we will also be able to deploy it for Web. I haven't run tests to confirm, but performance appears to be at least as good as native. Here are some additional benefits when using Flutter/Dart with VSCode:

• easy to set up and start coding
• easy to integrate/manage dependencies
• hot reload across multiple devices, on save
• auto-formatting
• quick-fix suggestions for syntax, etc. errors

Capacitor is a perfect tool for creating hybrid apps with any of the leading JS framework, so you don't have to worry about switching from JS to anything else. It also has a great ecosystem, as well as the native functions bridge plugins, most of them require zero-to-minimum effort to set them up. Unlike in React Native/Vue Native, you are not limited to specific components or logic, you are also free to choose any fitting UI kit, and the final product looks and behaves exactly the same regardless of the platform.

I'll second the recommendation to check out Capacitor, optionally with Ionic. Capacitor provides a sort of "electron for mobile" that runs web apps on iOS, Android, Desktop, and as a PWA on the web, giving you access to the full native functionality on each platform through plugins or custom native code. Ionic then provides a native-quality UI layer and opinionated developer experience that ultimately uses Capacitor under the hood.

Sounds like your team already has a lot of web experience and existing web code, so Capacitor on its own or with Ionic would be a great choice since it's a standard web environment and can run any JavaScript app.

i don't have any experience with the vue native what so ever but i think Quasar and Ionic are the best options for an HTML/CSS/JS based mobile app ionic has full support of vue and quasar is built on vue you may have to change some configurations in your project files

I don't know much about Xamarin but I know about PyQt and React Native.

However, I don't recommend PyQt because the apps made using PyQt are not that suitable for mobile apps. If you take a look at the PyQt interface, you will be able to see that the features are more of a desktop apps kind.

React Native uses JavaScript. React Native is immensely flexible in upgrading your apps because it allows you to formulate your app code into independent blocks.

In Xamarin, you have to write the code in .NET . The best thing about Xamarin is, that it extends the.NET developer platform with tools and libraries specifically for building apps for Android, iOS, tvOS, watchOS, macOS, and Windows

While the best choice for you depends on various factors but React Native app development is a promising overall choice. In today’s scenario, React Native has steady growth, flawless code structure, and brilliant and large community support. We suggest you go for React Native for your next project owing to its outstanding support from developers, easy availability, and cost-effectiveness.

It seems like your app is not really using any native functionality on the phone. I have experience with cross platform iOS & Android development. They are all really good tools! Xamarin (all the project on the website portfolio I attached) is awesome for accessing native functionality (NFC, Sensors, Bluetooth, etc), and I have built apps that have millions of downloads, some that hit Top 5 on Utilities, another that hit Top 50 in Finances. You just have to look at what your application intent is, it seems like it's just to read and post data. For that they are all pretty good, but you should also look into Ionic which may serve the same purpose

Choosing between ios/android and Flutter is not simple. Neither is a one-size-fit-all solution. It would be impossible to suggest one or the other without first analysing particular project’s requirements.

Choosing cross-platform development (Flutter) offers a number of advantages – lower cost, faster time to market, etc…, and if applied to the right type of project, will result in high-quality, marketable mobile product. In my opinion, stick with flutter and try to resolve those problems. Here are some useful links,

Map: *https://pub.dev/packages/mapbox_gl *https://www.raywenderlich.com/4466319-google-maps-for-flutter-tutorial-getting-started

Payment Service: *https://developer.squareup.com/docs *https://github.com/square/in-app-payments-flutter-plugin *https://pub.dev/packages/stripe_sdk

It's a bit late but I suggest staying on Flutter anyway. Though you might face troubles with APIs integration, overall development experience is better on Flutter, so you save some time & power on the project in general. Dunno if it's of any use to you, but as a prove I attach one of many Flutter vs RN comparison articles (you can find any other similar yourself on the web though), hope it helps you make a decision

can you discuss in more detail why cant you integrate that API?

Hey, If you are using Unity you are going to have to do the end to end development on Unity, you can directly build for android and iOS on Unity. I dont see how Flutter or React Native fit into this equation. Unity is a standalone engine. As for Social Chats, you could use Firebase or your own API and integrate that in Unity in C#

I agree with Sahil. If Unity is a requirement, best way is to use just that to create your app.

If you really want, it should be possible to use Flutter and Unity together. Using Flutter Unity Widget. Although I wouldn't recommend it just yet. It's too early days.

If you do end up using it, I would be very interested in reading about your experiences.

You can start by small steps with Flutter and after Unity. Flutter = best choice to build a small cross-platform mobile app. With or no flutter, use directly Unity. Y'll have complete control but it's harder for new mobile developers. Keep in mind, the requirement is Unity!

Well, the first resource I would recommend you is my upcoming book by Packt Publishing, "Professional React Native", but it's due late January next year :) . Now jokes aside (the book's real by the way :) ), the easiest way to build a iOS/Android/Web app with React Native is to do: npm install -g expo-cli expo init some-project cd some-project expo eject

You might have heard of Expo, but trust me, stay away from it. Expo highest value is that it's an already pre-configured 3 platforms environment, but if you don't eject then you're vendor-locked to what Expo has to offer in iOS and Android, which is very poor compared to going full React Native on these platforms, they can't even handle Google Sign In properly and by the way, even if your app is 10 lines of code your app size will be over 40 MB if you don't eject, yep it's that bad, plus the performance is regular and the loading times slow, not to mention that you're stuck with their build service which the free tier makes you wait for hours for a free build slot. It's important to note that when ejecting you don't lose the Web, you simply do expo start --web to start your dev environment and expo build:web to build a static website that you can serve with any web server. Regarding state management, don't bother with "lifting state up" philosophies mixed with Context API to manage your state, lifting state is a great pattern and helps your codebase, Context is great to avoid prop-drilling, but NEVER mix them to achieve app-wide state management, for that, simply go for Redux or MobX, the hype is all about Redux, but I consider MobX far better in many aspects. However, as you're getting new into this I would recommend you start with Redux AND PLEASE grab yourself npm install @manaflair/redux-batch so that you can batch updates and don't bring your app to a crawl. Forget that "connect HOC" thing with React-Redux, don't bother for a second with it, go with Hooks and useSelector and useDispatch and the likes, it will make your code SO much cleaner and smaller. Adopt clean and new Hooks philosophy, avoid writing class components as much as possible and write function components augmented with Hooks.