1 pointI find that in general layouts designed for GO or WebD always look fine on the desktop (not always true the the other way around!) My default design paradigm is to always use the Touch themes even for desktop layouts. This keeps the layout duplication to a minimum. Keep in mind there are aways exceptions where you will have to have duplicate layouts for Go and Desktop based on other demands (or workflow).
1 pointI have done exactly this, although using Windows tablets. You need to think differently... As you discovered FMServer will disconnect, so you need a solution that does not need to maintain a permanent connection to FMS. 1. Run a local datafile on iPad to collect the sign ins. 2. Connect to FMS only when you have some data to send - maybe as soon as employee has signed in, OR, 3. Connect to FMS using an OnTimer script - maybe every 5 minutes so the iPad doesn't stop users signing in immediately after the last employee. 4. If the connect to FMS fails then error trap and just wait to have another go. In my solution I refined the sign in so that OnTimer script was removed whilst signing in to prevent connection to FMS, then restart OnTimer once sign in complete. I have this working in a 200 employee company spread across 3 main building and 6 sign in tablets and there is high demand at shift starts/ends. The tablets are working 24x7 and are resilient to network failures and server offline events. They even run during power outs as the tablet are all battery powered. It can be done!
This leaderboard is set to Los Angeles/GMT-08:00