![MobileIron Virtual Smartphone Platform [EOL] vs. ZixOne report](https://www.peerspot.com/assets/media/images/icons/pdf-80836ec5.svg){kind=icon}
![MobileIron Virtual Smartphone Platform [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,f_auto,q_auto,w_64/671bvmknwdq3yrmveapeupho1rxu.jpg)
![MobileIron Virtual Smartphone Platform [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,f_auto,q_auto,w_30/671bvmknwdq3yrmveapeupho1rxu.jpg){kind=small}
![MobileIron Virtual Smartphone Platform [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,f_auto,q_auto,w_40/671bvmknwdq3yrmveapeupho1rxu.jpg){kind=small}
Focus onto the planning phase of the implementation. Prepare a list of your requirements regarding the restrictions (passcode, secure data access), use cases, what type of resources would your users like to acces from their mobile device. Per device and per user licensing are available, so you can decide which is the best for you. There are two type of implementation available: Connected Cloud and On-premise. In the first scenario MobileIron is responsible for the availability, the backup and the version upgrades of the Core. Make groups by the type of users and use active directory groups for assigning configs and policies. Prepare a list of the platforms you would like to support. Ask for a 30-day evaluation from MobileIron and check that it meets with your expectation and requirements. Mobileiron provide 0 day support for new versions of IOS, Android and Windows Phone. It is possible to create dynamic groups of configs and policies as per the user AD group membership and by device properties (platform, OS version, screen size,… more than 240 filter properties can be used)
