Alternative is to make a porting kit...

Create an Composr module for exporting bits of the same Composr site to Android/iOS code styles (parse PHP code, change ini files to string resource files, etc).

Have a standard remote-Composr framework for iOS and Android that has a set pattern of web service integration, and equivalent API functions (e.g. the forms API).

Allow mocking in the remote-Composr framework, so we can test prior to JSON API endpoints being implemented in Composr. Also allow caching.

(this doesn't really align with the above idea, but could be done in addition, and some percentage of work would be shared - the advantage is that it is a more straight-forward approach that is easier to hire for, and easier to work without constraints - the disadvantage is it doesn't automatically improve the Composr web mobile mode)

I've tagged this as 'performance' because I think this could be a lot more than great mobile support. I think by transferring basically just JSON from the server, handling template rendering client-side, we could massively improve performance.

Rather than trying to squeeze lots of features into Composr Mobile SDK (or trying to persuade Tapatalk to open up), it would be best to focus efforts on making the main web UI super-performant, as good as native apps. We could also then package that up with Phonegap if we wanted to.

Closing this, as I am opening up new cleaner issues, under the "Type: Mobile" tag.