However I am finding a few setbacks here and there, and another is the presentation differences between iOS and Android tablets.  It seems some "bar labels" aren't being handled correctly and it's difficult to know exactly what you're doing and where you are at.

For instance, on Android tablet, when I view a report named "Report" to view records, then proceed to select a record, then to edit a record, the bar at the top still says "Report", not the name of the form that's actually in play as I'm editing.  Also, the data listings (concatenations) in a report view seem confusing and not particularly useful.  Also, I have several child recordists, so, I have subforms, and some sets need an "image" field, and this is not supported with Android  .  The whole reason a user would perform data entry on a mobile device is to easily use the onboard camera to "scan in" documents. 

Zoho, you're SOooooo close to having a great developer application.  Allow programmatic child record bulk entry, and image fields in "subforms" on mobile devices and you've got a great product.  Otherwise, you're losing a lot potential customers.   Or better yet, give the developer a way to add child records without a subform this would solve a lot of problems (enhanced relationship module)

So, I'm wondering if there is anything a developer can do to remedy some of these issues relating to how the application works on tablets and smartphones, or are we completely at the mercy of the Zoho backend design/developer team?

I think I like the application better on iOS tablets then I do on Android tablets.  And this is a shame because my customers are 85% Android users with their handhelds, although most will do 80% of their data entry work with a full laptop.

I'm writing an application for the ultimate mobile people, truck drivers.  So, the ability to be flexible and widely accommodating is very critical.  But this is the reason we look to someone like Zoho Creator ... so we can avoid having to code several different mobile apps in a very complex code system.  So, I guess this is part of the tradeoff?