Is it acceptable to implement the application not through native elements, but through webview?

Question

iOS

Good afternoon.
Let's say I need to implement an application whose interface capabilities should be wider than the capabilities that xcode offers out of the box. The application itself is client-server, without a working Internet it is not functional. Therefore, I see three paths:
1. using native xcode solutions (app with limited features, X development time);
2. use webview (full-featured application, 0.1x development time);
3. use of non-native (self-written) xcode solutions (full-functional application, 10x development time);
Of course, each path has its pros and cons: in development time, in functionality, complexity of development and support.
My question is how acceptablego the second way?
Thanks for your opinions and experiences.

Answer 1

As a developer, never used this path.
As a user, I regularly observe this approach at the payment stages in various applications, and for some reason it is very popular with airline applications in the ticket purchase section.
It should be borne in mind that the native look&feel will never be fully implemented, an experienced user will notice the difference, and it will work more slowly. For iOS, the user's feeling is extremely important, if he downloads an application from the App Store, he expects a certain workflow, speed of work, and at least some offline-mode.
If you do not want to bother with ObjC, I would advise you to make a web application for Safari, most of the possible native applications are now available for them (icon on the home screen, notifications, work with the physical abilities of the device)