Does it make sense to write applications in nativescript or reactnative if the customer does not know what he wants in the future from the new functionality?

Question

Mobile development

Hello, our team has written a client-server application (angular 4 + java backend), there was a requirement from the customer that he wants a mobile application. Not a problem, the UI has a responsive design and a mobile menu and user-friendly UX, and here we stuffed the iframe into the Ionic 2 framework, assembled it for all platforms and gave it away. And then the customer had a wishlist:
1. Working with bluetooth with other devices through the application function (well, ok, even Ionic can do this)
2. Opening someone else's application in your application (a third-party application that is written in Qt and draws 3D graphics)
3. The second can or should be interchanged with the third, there are Qt source codes for this application that renders 3D graphics (there is also a correspondence with these developers of this application), you need to put it into our application as a function and assemble it into one executable application.
On the second point, I stuck, is it possible to implement this in NativeScript or ReactNative? It's just that the UI is already written on the web and I would like to use my team of front-end developers (there are three of us) as much as possible so that the mobile application can really work and at the same time we can write it ourselves. I read that working with 3D is not implemented in any way and there are no working examples in this direction on NS and RN. And there are no examples of opening an app within an app.
Or is it easier to hire a Qt developer who will do the same, but 100% cover any task of mobile development for all platforms?

Answer 1

What's the difference to you?
You can redo it from scratch if the platform does not allow another small Wishlist.
The only question is how he is willing to pay.
The formula is known:
Flexible for all Wishlist universal method - more expensive to develop from the very beginning.
Cheap methods that allow you to start quickly - then they will cost very, very expensive.
If you want to optimize this, your task is to agree on the amounts with the customers.
And to convey to him - that the size of the hotel is not directly related to the cost of work.
If he does not immediately tell all his Wishlist, then he may run into a situation that the next "Small Change" is too difficult to implement into an existing project.
If he wants to immediately fix possible problems in the future, he needs to immediately develop on a more serious expensive platform.
Many customers adequately approach the choice of the method - it is cheaper right away, but extremely expensive later, or the average price is always stable.
Some are even cheaper. But then, when they squeeze in a millionth Wishlist, they continue to work out the already millionth accounts. Since a lot of money is invested and he has nowhere to go already.
But a normal developer must respectfully explain to the customer the possible options IN ADVANCE. For this is the choice of the customer, not the developer.
The choice of the developer here is to offer the customer those technology options that the developer can work with.