Should I stop developing and maintaining iOS and Android (which will incorporate functions such as maps and cameras) just by using Gawa Native (WebView)?

Asked 2 years ago, Updated 2 years ago, 38 views

I have been developing iOS apps on my own, and I have released some of them.

However, I have no experience in developing Android, and I have a request for the Android version in response to the response from the users.

I'm always in a muddled mood without being able to respond to your request.

*I also want to study Android, but even if I study, I think it's a little unrealistic considering that I do both iOS and Android by myself.I'm not making enough money to hire people, so I'll be alone for the time being.

Therefore, from the next development, we are thinking that it will be solved if we develop it as a Gawa native (WebView).

As I am a native speaker of Gawa, I read articles such as whether I can use iOS and Android's unique functions such as maps and cameras, so I think it's great.

Operating speed problem was often cited as a disadvantage.

However, I am thinking of shifting to this side in the future because of the low cost of learning.

Based on the above, we would like to hear your feedback and experience in developing and maintaining Gawa native speakers in the future.

Gawa native speakers are convenient, but in fact, they often seem to be...

The direction of the next app to be developed is still vague, but I will briefly list the functions that I have developed so far.
·Display location information on GoogleMap
·Take pictures with the camera
·Send push notification
·It doesn't go to Instagram, but it's a photo-main app

The goal is to get 1 million users through the app (of course more than that), so I would appreciate it if you could include the perspective of whether you can endure it or not.

I'm particularly concerned about the fact that it's well drawn on iOS, but not on Android, and that it's hard for each version.

ios android

2022-09-30 20:13

1 Answers

If you are using WebView for Android apps, you should be careful when deciding on the target version of the app.

There are the following differences between Android operating systems:

  • Android up to 4.3, WebView based on Android browser
  • Chromium-based WebView from Android 4.4
  • With WebView disconnected from the operating system from Android 5.0, you can update via the Google Play store, so you don't have to wait for each carrier to update the operating system

First of all, why don't you check if the HTML5 API you are thinking of using is compatible?

As you said, Android often experiences problems with drawing for each version and JavaScript processing is not working well.
Another possible solution is to use CROSSWALK.
*Available for Android 4.0 or later.

This is like incorporating a whole web browser into an app, so there is a disadvantage of increasing the size of the app.
Also, if users upgrade their OS version or update WebView via the Google Play store, the app will not be affected.

However, using CROSSWALK does not necessarily mean that rendering speed is fast.
For your information, I will share the results of my previous verification.

Personally, even if I developed it as a full native, I usually need OS-specific support, so
I think it's ants that reduce man-hours by developing hybrid apps using WebView.

I hope it will be helpful even a little.


2022-09-30 20:13

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.