Use Flutter and Firebase as a backend service, Firebase also helps to speed up the development and rollout of the app. The cloud-hosted NoSQL database provides a real-time database that helps you store and synchronize data between the clients. This indeed makes it easier for you to access the data using any of the devices.

Hi there, for cross-platform functionality in terms of 3D assets if any, echo3D can help you with that. It's 3D asset management on the cloud so you can write your references to the objects and update them in the echo3D web browser. echo3D is not yet on this platform but it will be soon!

I think that React Native or Vue Native is the best choice for modern cross-platform mobile applications. And both of these frameworks have a large community. Apache Cordova was the pioneer in this way. We used it in projects in 2014. Ionic is also an old tool and in 2014 it was based at Apache Cordova. I don't think that it has so a big community like React Native or Vue Native.

For a web system, React or Vue is a good and modern choice too.

No shade on the hard work of/on Ionic and Cordova over the years, but they are not the future and you will be going down a dead-end for maintainability going forward. React Native is an excellent bridge for any pre-existing JavaScript/TypeScript skills you might already have from web development.

Flutter is worth considering as a close second but I would recommend RN for the above reasons. Also consider using Expo to ease your build process.

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 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.

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 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

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 would never recommend you to go with Ionic, Because of the User experience it provides is subpar. Flutter is most promising, Can be easily used to develop great user experience in no time. React native is also good, but it's phasing out in my opinion, while Ionic has already phased out. Flutter also provides great developer experience, resulting in fast and productive developers. I would have to press hard to think of a CON about flutter when recommending it for your needs.

Maturity, Community, Facility, Libs React Native is the principal platform of mobile cross-platform development today, Flutter is it's a promise.

Even if React Native is older (I didn't say mature) you should go for Flutter, It's works really well and the developer experience is great (auto-completion, plugin etc). I spent years with React Native and now I am using Flutter and I don't regret It. Even if you have to learn a new language, It's pretty simple even more If you know some OOP, Java and Javascript ES6 syntax in some case. One other advantage is the facility to design app in Flutter, you have widgets for everything and you can adapt any design made by your designer. For example you can't make a simple custom box shadow with React-Native ...

Flutter is built on DART which is written in GO. GO compiles to binary. Hence is faster than any java based framework. It provides superior performance and has a simplified UI process for designing apps.

I don‘t have practical experience with flutter but between ionic and react native I‘d say both a perfectly viable options and we have used both for a number of production apps. We normally go with ionic on capacitor because we build a lot of pwa/web apps so we can use the same code for all. We don‘t use much of ionic elements, we do most styles on our own.

The comments that the user experience is bad I cannot agree with. A well designed and developed ionic apo can hardly be distinguished from a native app. But obviously that depends also on the usecase and type of app.

I hope this helps

It depends also on your team skills. Flutter is fast to learn, fast to develop with and the performance is much better in comparison to React. If your team is already highly skilled in React Native it could be the better option - if not Flutter is my 100% recommendation. We rapidly prototype and deliver MVPs with Flutter since two years.

I think you should chose between Flutter and Ionic. With those two options, the main question is about graphs and performance. Are they really important for your application? If the answer is yes, your tool is Flutter but, if the answer is that you need an easy tool to create an app with some basic components I would choose Ionic. You have a library with lots of components that you can use and they have native UI by default (for Android and iOS).

You will find more support if you use Ionic with Angular as frontend framework (you have the option to use Vue or React but this is a new feature for Ionic and I think there are more difficult to learn than Angular).

You can develop and debug the majority of features on PC (I don't know if that is possible with Flutter). And when you will finish the app, create iOS and Android versions is simple.

It's probably not relevant anymore, but I think Ionic with Angular as the frontend is the right choice. For IDE I would choose Visual Studio Code. You can just create a basic web application with responsive design, which is already included if you are going to use Ionic components with Material Design to create your app. You don't need to know Swift, you don't even have to create mobile apps, just create a responsive (Ionic already is) web app, or PWA. Upon browsing your website from a mobile device for example using google chrome, you will be prompted to create a shortcut of the website in your mobile phone. After you do this, there will be an icon in your phone that looks like an icon to launch an app, it will launch your website in full screen mode - for the user's perspective it will look like he is using a native app. Access https://ionicframework.com/docs/angular/pwa from your android chrome browser, go to tab options (3 vertical dots), click on Add to Home screen. When you launch the website from the shortcut, you'll see that it behaves and looks like a native app.

Flutter is easy to use and easy to understand. Once you have completed the android platform, you can easily build it to ios, Web or desktop on a single code base.

1. Electron is for desktop apps, so not useful for you.
2. Flutter has better performance, but Ionic is decent as well, I would use Ionic unless you're making a game or graphic-intensive app.
3. Ionic is more flexible since you have the whole NPM ecosystem available, while flutter is more recent, thus libraries for it are less in quantity and battle-tested than the ones in NPM.
4. Ionic 4 introduced CSS variables, which improved immensely the theming process for the app, which was the hardest issue Ionic development had.
5. Ionic has extended to many frameworks so it's compatible with Angular and React frameworks, meaning more flexibility, personally I would recommend Ionic with Angular over React since it's more suited to enterprise-level apps.

Hi there. So Electron embeds everything in a webview, which means that what you would have to develop would be a Node project most probably. Ionic does the same (kindof but won't bore you with specifics) but it does it much more efficiently. Usually you do Ionic apps with JS frameworks like Angular or React (this one recently added). Flutter on the other hand does native apps, it does it really good but it's support for Web is in beta and it's relatively simple to setup if you already know the SDK and the environment.

My recommendation would be that you do your app using Angular/Ionic if you reaaally need the multi-platform environment and there's different reasons in this case:

• Since it's a graduation project you need it to be as simple as it can be and adding a new technology adds to the learning curve.
• Flutter is great if you have different complex UI or if you have specific performance needs that require native support and in your case it does not seem like you need that.
• Flutter is also an incredibly powerful tool but it's learning curve might be tricky if you have not developed native apps before so I wouldn't recommend you start off like this if you have time sensitive projects like a graduation project. It does have great docs and an awesome community but I'd suggest you stick as close to what you know as you can.
• Ionic/Angular uses Typescript (a type javascript wrapper) and Angular (JS framework) so you will have to learn a little bit but if you already know HTML, CSS and Javascript you won't have that much of a hard time. Also there's quite a lot in terms of documentation and tooling already tested around this combination.
• Ionic/Angular has a really good CLI that helps you stick to the architecture they recommend so you wouldn't have to worry about it that much.
• Ionic/Angular helps you test either locally in the web browser as well as your devices which is in the end what you want if you are looking for a multi-platform system. Flutter also does this but is not quite in a stable state (yet!).

Anyway, in the end, if you go for the multi-platform suggestion I think, because of time you would be better off with Ionic. If you decide that you don't need that as of right now (which is fine as well) you can start with just the Android app and plan on the different things you might eventually need like a website or other different stuff. Cheers!