If you need to support multiple UI formats, we recommend designing your UI file using the highest likely resolution as your base. From there, you can create a hybrid file that accommodates both tablet and smartphone layouts.

For example, if you design a 1024×768 template for tablets (such as iPad), you can include additional pages or popup layouts with larger, touch-friendly buttons for smartphones. These elements will scale down to fit smaller screens while maintaining usability. The main trade-off is that your design will remain fixed in either landscape or portrait orientation, depending on your chosen base template.

Additionally, you can manually transfer UI files when an alternate file is required instead of the one hosted on the control system. TPControl for Apple supports two UI file slots, while Android supports one. These slots operate independently from the slot used for retrieved BYOD files.

You can recall any file slot (including the currently active BYOD slot) using the TP4FileSlot API command (see TPControl – API Commands for more details, as well as the TPC API Profile examples; the TP4 example demonstrates usage).

For a reference implementation, you can review a sample TP4 file that demonstrates how a single design can support both tablet and smartphone devices: Tablet Smartphone Hybrid TP4 File

This type of hybrid design is well-suited for use as a hosted BYOD file on a BYOD-licensed NetLinx master.