Resco Mobile CRM platform specifics

New updates: Whenever a new update is created by Resco, it has to be approved by the app store. Google Play (Android) is, from our experience, very fast by doing so. Apple takes its time. That’s why, when a new app is released, Android users can get it the next day while iOS users could wait for 2 weeks. This will be noticeable when there is an unexpected compatibility issue with new OS version.

Advanced customizations/development: Android is generally a more open platform because it allows the application (in this case, Resco Mobile CRM) to communicate with other applications and the system. iOS does not allow this type of integration.

Because of this, call import (creating activities from received/made/missed phone calls) works only on Android devices. Other platforms are only able to track phone calls made directly from the Mobile CRM app.

Features: There is also a slight difference in the functionality of Resco Mobile CRM application across different platforms. These differences come mainly from the fact that we implement features in a pretty quick pace, which means a feature that is done by the release date on one platform only gets out there anyway (the rest will follow afterwards).

Other differences are because of the platform specifics and restrictions.

apple_small_icon iOS (iPhone/iPad)

  • uses Apple maps
  • can run for max. 10 minutes in the background (therefore not advisable to do the first synchronization in the background)
  • takes a week or more for the new app to be out in the store

android_small_icon Android

  • uses Google Maps
  • only platform with call import
  • the print report functionality only available on Android 4+
  • supported MDM: Symantec
  • takes a day or two to be on the Google Play store

windows_small_icon Windows

  • uses Bing map
  • no calendar sharing (syncing Mobile CRM calendar with a system calendar to fuse personal and professionals schedules)

    Blackberry

  •  Resco Mobile CRM does support Blackberry powered by Android

 

windows-phone-icon

Windows Phone – we have waited for Windows 10 to come along and save this rather unfortunate platform (better upgrade your phones to Windows 10 to get the new features).

Windows Mobile – if you have devices with Windows Mobile, think about updating them (to something else); it’s quite and old and limited technology-wise.

The exception to the rule: Devices that have unlicensed Android or do not support Google maps (happens in China) are only able to run a different version of our app (a one that does not include maps and is available upon request).

Hardware requirements

Available space: Resco Mobile CRM requires as much database space as is decided by the system admin (by using sync filters). There’s no way you can copy the whole CRM database into a phone or a tablet (you just don’t have that much memory), so synchronization filters need to say how much of the data will be stored in the local database for an offline access. This can be as little as 100MB. Records don’t take much from the available space, attachments do.

Note: the current size of app itself is 37.7 MB on iOS (18MB on Android). Compared to Chrome with 82,6MB and OneNote with 190MB, it’s quite small.

Minimum 512MB RAM (1GB is better): A database of 15,000 records can run very smoothly on a 512MB RAM, whereas a database of 2.5 million records can display average performance on a 1GB RAM. In most cases, it depends on the way you’ll use it.

Camera autofocus is needed for barcode and QR code scanning. So bear this in mind in case you want to utilize this feature.

GPS location system for tracking of activities, updating addresses, navigating, etc. You need for the device to have a GPS module in case you want to utilize the maps. We have implemented a fix for devices that don’t have embedded GPS (such as iPad 2) – it gets the coordinates via WI-Fi. But this will always be less accurate and much slower than actual GPS.