Form Appearance on Mobile

For sake of clients viewing portions of their own data, we embed Quickbase forms into a portal/viewer.  The forms are specified through embedded URL's containing RID, DFID and of course, IFV=1.  Unfortunately, the mobile side of Quickbase just isn't on the same playing field with the browser based version, in terms of controlling what is/isn't visible, among other things.  The bottom line is that I need to show an alternate form (blank form with message saying 'not mobile compatible' or something of that nature) when the form is accessed via mobile.

KEEP IN MIND that controlling what form is seen via role association for EOTI is NOT an option here.  In order to make the data consumable, we use (5) different forms, containing topic based data, and formatted for best consumption of the particular dataset.  The only way I know of to do this is by dictating which forms are viewed through DFID being specified in the URL.  

Also, these URL's are not visible to the client, and I won't change that.  They are embedded behind our client portal viewer, and associated with buttons/tabs that call up the embedded form without disclosing the URL to the client (or competitor).  

Given that the specific form is called up via DFID in the URL, is there any way to tell Quickbase to show completely different information, or simply hide all but one information field or something, when accessed via mobile device?  Either that, or force the full form to be shown on mobile device and ignore mobile versions? That would not make the forms very useable, but at least it would force the mobile version to conform to the rules from the full version.  (i.e. ability to get to 'home' buttons and other QB interface things that can't be easily hidden, especially with new restrictions from QB, to hide via IFV=1 command like the full version does).

At this point, I'm perfectly fine with blocking the entire client access system unless they're on a computer, and simply displaying a message that says 'these records cannot be accessed from mobile devices'.  Not ideal, but I'm running out of options.

------------------------------
Joe Hargrave
------------------------------