Determine which kind of app wrapping system we'll use

[charlesstrange2]

based on

• cost
• penitential automation
• mobile OS legacy version support
• we don't have to recode everything

Acceptance criteria

• [x] we have reviewed some options
• [x] we have a recommendable service
• [x] we have a service signed off to progress with

Plan

• [x] enumerate the current app wrapper systems
• [x] examine them with the above criteria in mind
• [x] pick one
• [x] get it signed off

[charlesstrange2]

Adobe Phonegap Build

https://build.phonegap.com/

• is free for one app (and, oddly, can't find prices...), which is all we need
• can be automated, thought the docs are... less than clear
• we have past experience with it, but still requires configuration
• supports google/apple suggested minimums

[charlesstrange2]

Apache Cordova

https://cordova.apache.org/

• it's free
• not easily automated
• it's just like build
• we have more control
• it's Adobe Phonegap Build, but with all the self hosting hardware pain

[charlesstrange2]

Options that would require significant redevelopment work

• Flutter https://flutter.dev/docs/get-started/web - "not ready for production"; their words
• Framework7 https://framework7.io/docs/custom-build.html - it's a whole new framework
• Ionic https://ionicframework.com - it's a whole new framework
• React native https://facebook.github.io/react-native - requires rewriting a lot
• Xamarin https://dotnet.microsoft.com/apps/xamarin/cross-platform - wants to eat C++/C# rather than html5/css/js
• Appcelerator Titanium ; builds down to native, is a specific toolkit.

[charlesstrange2]

@marxian Looks like adobe phonegap is the best "fit" for now

[charlesstrange2]

Not seeing any other options at this stage, will proceed with phonegapp