Appeon Mobile UI Resizing

    By: Mr. Yakov Werde on Feb 02, 2014

    In this article, we examine the Appeon Mobile UI resizing mechanisms that you can employ when designing a UI for a specific device category. The mechanisms that will be discussed include device type restriction, the PFC resize service, the AEM Mobile UI Resizing Tool and a code based resize service.

    Mobile applications fit into two categories, Phone and Tablet. Phone apps are usually single purposed with simple targeted UIs while table apps are multi-purposed with complex large UIs. It is therefore preferable to design a UI for a specific device category. Appeon Mobile allows a developer to restrict an app to a particular device type at deploy time, by defining three device type deployment settings, Smartphone, Tablet or Both.

    On the device, Appeon Workspace will refuse to run an app with an incompatible device type specification.  A message display results when attempting to run a tablet app on a phone.

    Because of legacy application migration considerations, Appeon supports deploying apps with two types of device UIs. (1) Apps with UIs specifically designed for mobile device display form factor (phone or tablet) and (2) Apps with Client/Server UIs directly deployed to mobile devices. In the first instance, UI elements were designed for the target device type, but since various form factors are available within the category, minor runtime visual adjustments might be necessary to accommodate small size changes between specific device displays. In the second instance the entire UI requires automated resize treatment in order to reasonably render on a mobile display.


    Login to read the article. Not a member? Create a free account!

    Released: February 2, 2014, 11:35 am | Updated: March 5, 2014, 11:04 am
    Keywords: PowerBuilder Article | Technical Journal | Appeon | Appeon Mobile | Development | eLearnIT | PowerBuilder | Yakov Werde




    Copyright © 2014 ISUG-TECH. All Rights Reserved
    All material, files, logos and trademarks within this site are copyright their respective organizations

    Terms of Service - Privacy Policy - Contact the Help Desk