• Introduction
  • Dev Environment Setup
  • Developing Apps
  • Data Handling
  • Device Capabilities
  • Testing & Debugging
  • Extending
Warning Older Docs! - You are viewing documentation for a previous released version of RhoMobile Suite.

RMS 7.3 Supported Platforms

The RhoMobile Suite (RMS) is an integrated development environment for Mac OS X and Windows development hosts that can target multiple mobile-device platforms from a single code base. RhoMobile apps employ an HTML front-end that presents the UI component and passes device calls through to the underlying hardware. RhoStudio also supports native app development.

Supported Mobile-Device Platforms

Device image Operating system family Device(s) Operating System(s)
Sailfish From 2.1.1
Android Zebra devices (see below), third-party devices (ARM, ARM64 and x86) Android 4.4 to 9: KitKat, Lollipop, Marshmallow, Nougat, Oreo, Pie
Android Third-party consumer tablets and smartphones (ARM, ARM64 and x86) Android 4.4 to 9: KitKat, Lollipop, Marshmallow, Nougat, Oreo, Pie
Apple iOS iPad, iPhone ( up to XS, XS Max, XR ), iPod Touch iOS 6, iOS 7, iOS 8, iOS 9, iOS10, iOS 11, iOS 12
Windows Mobile/CE Zebra devices (see below), third-party devices WM6.x Pro, WM 6.0 Std, WinCE 5, WinCE 6, WinCE 7, WinXPe
Windows Third-party laptops, tablets and desktops Windows XP, Windows 7, Windows 8, Windows 8.1, Windows 10, UWP

Supported Zebra Devices

RMS 7.3 has been approved for building apps that target the following Zebra Enterprise Mobility devices:

Mobile Computers

Device image Device family Supported model(s) Operating system(s)
ES400 ES400 Windows Embedded Handheld 6.5
ET1 ET1 (Enterprise Tablet), ET1 WAN Android 2.3 (Gingerbread),
Android 4.1 (JellyBean)
MC2100* MC2100, MC2180 Windows CE 6.0 Core
MC3100 MC3100R, MC3100S, MC3190G, MC3190R, MC3190S, MC3190Z Windows CE 6.0 Professional,
Windows Embedded Handheld 6.5
MC32N0 MC32N0 Windows CE 7.0,
Android 4.1 (JellyBean)
MC40 MC40 Android 4.4 (KitKat)
TC51/52 TC51/52 Android 6.0 (Marshmallow),
Android 7.0 (Lollipop),
Android 8.0 (Oreo)
TC55 TC55 Android 4.1 (JellyBean),
Android 4.4 (KitKat)
TC56 TC56 Android 6.0 (Marshmallow)
TC70 TC70 GA2 (rebranded device) Android 4.4 (KitKat),
Android 5.1 (Lollipop),
Android 6.0 (Marshmallow)
TC75 TC75 Android 4.4 (KitKat),
Android 5.1 (Lollipop)
TC8000 TC8000 Android 4.4 (KitKat),
Android 5.1 (Lollipop)
MC17 MC17 Windows CE 7.0,
Android 4.4 (KitKat),
Android 5.1 (Lollipop)
MC18 MC18 Windows CE 7.0,
Android 4.4 (KitKat),
Android 5.1 (Lollipop)
WAP4 WorkAbout Pro 4 Windows CE 6.0
MC45 MC45 Windows Embedded Handheld 6.5
MC55 MC5574, MC5590 Windows Embedded Handheld 6.5
MC55A0 MC55A0 Windows Embedded Handheld 6.5
MC55N0 MC55N0 Windows Embedded Handheld 6.5
MC65 MC659B Windows Embedded Handheld 6.5
MC67 MC67 Windows Embedded Handheld 6.5,
Android 4.1 (JelyBean)
MC70 MC7004, MC7090, MC7094, MC7095 Windows Mobile 6.1
MC75 MC7506, MC7508, MC7596, MC7598 Windows Embedded Handheld 6.5
MC75a MC75A0, MC75A6, MC75A8 Windows Embedded Handheld 6.5
MC9100 MC9190-G, MC9190-Z Windows CE 6.0 Professional,
Windows Embedded Handheld 6.5
MC9200 MC92N0 Android 4.4 (KitKat),
Windows CE 7.0,
Windows Embedded Handheld 6.5
MC9500 MC9590, MC9596, MC9598, MC959B (WM6.1) Windows Mobile 6.1, Windows Embedded Handheld 6.5

Vehicle Computers

Device image Device family Supported model(s) Operating system(s)
VC6000 VC6000, VC6096 Windows Embedded Handheld 6.5
VC70 VC70 Windows CE 7.0

Micro Kiosks

Device image Device family Supported model(s) Operating system(s)
MK3100 MK3100, MK3190 Windows CE 7.0

Wearable Computers

Device image Device family Supported model(s) Operating system(s)
WT41N0 WT41N0 Windows CE 7.0

Device Memory and Other Considerations

Memory constraints are important to consider, particularly when targeting the older devices supported by RhoElements. The following points might be helpful to keep in mind:

  • Rhodes apps require a minimum of 128MB physical device RAM

  • The more Rhodes apps running on a device, the greater its memory requirement; consider using TabBar to combine several individual apps

  • For low-end Zebra CE devices, try using Control Panel to increase available program memory

  • Limiting the use of JavaScript frameworks will minimize an app’s RAM footprint

  • Don’t rely too heavily on performance tests for JavaScript and CSS found online unless they’re written specifically for mobile devices

  • An active RhoMobile developer community offers forums, blogs, webinars and other useful resources to aid in your development efforts

Compatibility Alerts

  • RMS 7.3 supports printing via USB from Android apps to a subset of Zebra printers that support USB printing.

  • The TC55 supports 4.0 APIs and only a subset of 2.2 APIs. Applications developed using certain 2.2 APIs might need to be rebuilt using a newer version of the API. For example, apps built with the 2.2 Scanner API must now use the 6.x Barcode API. Please consult the migration table for more information.

  • The MC3190-Z and MC9190-Z devices require an RFID plugin to be installed separately. This plug-in was originally developed for RhoElements version 2.2 but is still supported.

  • Only local development is supported for Micro Kiosk (MK) devices. Zebra development options for supported MK devices include RhoMobile Suite and Rho Browser.


Deprecated Zebra Devices

The following Zebra Devices are not supported in RMS 6.0 and later (but can still be targeted by RMS versions earlier than 5.1):

Mobile Computers

Device image Device family Deprecated model(s) Operating system(s)
MC3000 MC3000 (CE 5.0 only), MC3090 Windows CE 5.0
Windows Mobile 6.1
MC9000 MC9090, MC9097, MC9094 Windows CE 5.0
Windows Mobile 6.1

Micro Kiosks

Device image Device family Deprecated model(s) Operating system(s)
MK3000 MK3000, MK3090 Windows CE 5.0
MK4000 MK4000, MK4090 Windows CE 5.0

Vehicle Computers

Device image Device family Deprecated model(s) Operating system(s)
VC5090 VC5090 Windows CE 5.0

Wearable Computers

Device image Device family Deprecated model(s) Operating system(s)
WT4090 WT4070, WT4090 Windows CE 5.0
Back to Top