Posted by MickC on March 22, 2021 at 7:08am
I'd be interested to chat with anyone with experience in developing a "standalone mobile web app that talks to Drupal using web services" as described here
https://www.drupal.org/docs/mobile-drupal-sites/web-based-mobile-apps
Which app platform works best with IOS? Android?
Thanks

Comments
I builr 2 apps in the past
I builr 2 apps in the past with Cordova. Both apps took advantage of web services. Cordova was the only platform I knew then but these days I might try building the same app with RN or Flutter. I was told Flutter is faster.
I built 2 apps in the past
I built 2 apps in the past with Cordova. Both apps took advantage of web services. Cordova was the only platform I knew then but these days I might try building the same app with RN or Flutter. I was told Flutter is faster.
60 vs 60
Hi Kartagis,
Looks like nowadays React and Flutter is quite the same with the framerate which is 60.
I remember Flutter was faster and more responsive than React but would be good to check the recent performance statistics.
Hope that helps.
Director @ Passion Ventures Digital
Digital Architect | Acquia & Amazon AWS Certified
www.jakubmroz.com
Thanks guys really appreciate
Thanks guys really appreciate the feedback.
Just saw this post from 2015:
https://groups.drupal.org/node/469193#comment-1105128
@VladimirAus do you have any updates since then?
Would Cordova still be high on your list?
Thanks
Mobile app development in 2021
Hey @MickC.
The only thing that didn't change for the last 6 years:
* YOU WON'T SAVE ANY TIME by building your application in HTML
Cordova is still active project under Apache wing (https://cordova.apache.org/) but it is great for prototypes and if you want that cheap and jerky HTML app feel. Every provider including Facebook (builder and advocate for React) since then moved on onto building native apps (coding in Java/Kotlin (for Android) and Swift/Objective C (for iOS).
* https://developer.apple.com/swift/
* https://developer.android.com/
These days I recommend the following:
* Unless you have 2 x your website budget + extra budget room to move, stick to the web presence. Invest money into testing your website on mobile devices (real testing) and make sure it is mobile first (frameworks like Boostrap 5 is great help here).
* Think twice if you want to build native app. Are there any features that you cannot implement on the web? Implement those features as a part of your website. If you still have 2x your website bidget, invest into accessibility and more mobile testing.
* Think three times if you want to build native app. If your website is great and accessible on mobile and you still want to build an app and have a budget to do so, pick one OS and build native app.
Things to keep in mind:
* Mobile apps always cost more to build especially the first time around than websites
* Mobile apps always take more time to build especially the first time around
* Frustration comes after you first 50% is complete and you start facing real challenges that are not well covered in documentaion and examples, e.g. automation of phone camera, GPS operation in background vs foreground modes, etc.
* Completeing mobile app is only 50% of the whole process. You would need to take care of app store registrations and paperwork (e.g. as Australian you cannot release free app in Australia unless you have local business number), compulsory branding in app store formats (logos, screenshots, videos, descriptions).
As a bonus, if you want to experiment, checkout Fullter from Google:
* https://flutter.dev/
Hope that helps.
Thanks @VladimirAus that's
Thanks @VladimirAus that's great, thanks for sharing your experience, and will take your advice on board.