cancel
Showing results for 
Search instead for 
Did you mean: 

Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Highlighted
Grill Chef
Grill Chef

Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

1 Solution

Accepted Solutions
Highlighted
Staff Chef
Staff Chef

Re: Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

Hi Adam, I also found this on the Community for you.

Best Practice Approach for Better Performance of the ServiceMax iPad Application

Below are best practices for Technician users to follow for better performance of the ServiceMax iPad application.

  1. Do not run multiple applications in the backend on iPad
  2. Do not use any hotspot connection on iPad
  3. If possible, do a manual data sync at least twice a day when the connectivity is good.  Do this preferably once when you start your day so that you have up-to-date information on your schedule for the day, and once at the end of your work day, so that all your completed work is updated in the server.
  4. Perform the Config sync at least once in a week for better performance of iPad app
  5. Data purge every two weeks
  6. A good Internet connection is necessary for optimum iPad performance

AND I will add setting up Capturing Technicians locations (lat and long) regularly will kill the battery.

Let us know how you get on with your testing with performance and the best recommendation I can give is to try to stress test it with actual data volumes and as real as possible data. You will see the cracks then.

Regards, Richard

~If my post was useful, please give me a thumbs up! Mark correct answers as 'solutions' so we can all find answers faster!~

View solution in original post

0 Likes
Reply
Highlighted
Staff Chef
Staff Chef

Re: Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

Hi Adam Homoly​, there are a number of areas you can look at,

- how many days worth of events and related records you download (both for the future and the past)

- the download criteria and advanced download criteria you have setup. Make sure none are open ended. We had a few years ago one that was looking at records owned by the engineer and it wasn't considering when they were created or their status. So the volumes grew and grew until it went boom.

- Signature capture tends to make the sync take a long time.

Are you experiencing slowness? If so what exactly is it affecting?

Regards, Richard

~If my post was useful, please give me a thumbs up! Mark correct answers as 'solutions' so we can all find answers faster!~
0 Likes
Reply
Highlighted
Grill Chef
Grill Chef

Re: Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

We are still in the implementation stages and have not gone live yet. I just wanted an recommendation prior to pulling the trigger so there are no surprises for our techs when we do go live. Thanks for the tips!

0 Likes
Reply
Highlighted
Staff Chef
Staff Chef

Re: Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

Hi Adam, I also found this on the Community for you.

Best Practice Approach for Better Performance of the ServiceMax iPad Application

Below are best practices for Technician users to follow for better performance of the ServiceMax iPad application.

  1. Do not run multiple applications in the backend on iPad
  2. Do not use any hotspot connection on iPad
  3. If possible, do a manual data sync at least twice a day when the connectivity is good.  Do this preferably once when you start your day so that you have up-to-date information on your schedule for the day, and once at the end of your work day, so that all your completed work is updated in the server.
  4. Perform the Config sync at least once in a week for better performance of iPad app
  5. Data purge every two weeks
  6. A good Internet connection is necessary for optimum iPad performance

AND I will add setting up Capturing Technicians locations (lat and long) regularly will kill the battery.

Let us know how you get on with your testing with performance and the best recommendation I can give is to try to stress test it with actual data volumes and as real as possible data. You will see the cracks then.

Regards, Richard

~If my post was useful, please give me a thumbs up! Mark correct answers as 'solutions' so we can all find answers faster!~

View solution in original post

0 Likes
Reply
Highlighted
Pastry Chef
Pastry Chef

Re: Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

You can also use the mobile supportability tool to analyse the query times and number of records for your data sets in your mobile configuration. Very useful for identifying troublesome objects.

Access it here and login as the user (not with your admin account): https://msupport.servicemax.com/msupport/loginTarget

Highlighted
Grill Chef
Grill Chef

Re: Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

Good stuff, thx!

Highlighted
Pastry Chef
Pastry Chef

Re: Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

Hi Adam

One setting in Smx helped us a lot, Set19, Servicemax Ipad Client, Synchronisation, which turn on or off the Aggressive Syncs; our techs often work in factory environments, where its often difficult to get a good phone connection and hence a slow internet speed. With aggressive syncs on, the iPad will try to do a regular sync, and if it doesn't have a good connection these syncs can be very slow, or they fail, this in turn leads to the sync requests being queued, and this can lead to loss of data, or duplicate records, from when the system tries to recover itself.

With the aggressive syncs off, the tech can manually sync when he knows he has a good connection, and i have to say the app is very good at working offline, so doing these selective syncs fixed a lot of our problems we were seeing.

Other than that, i agree with the other advice give, keep your data cube as small as possible, and make sure syncs are done on a regular basis.

Thanks

Russ

0 Likes
Reply
Highlighted
Pastry Chef
Pastry Chef

Re: Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

Hi Russ, the way I understood aggressive sync was this:

  • With it switched on, each time you save a single record, it will sync this record, but also evaluate the download criteria and check if anything else has changed and sync that too.
  • With it switched off, each time you save a single record, it will only sync this record and not everything else. Only when it periodically does a full sync or you force it to, does it sync all the other data

For our business, we have it switched on because we have a self-dispatch model so a lot of other data is constantly changing, such as new work orders are created or reassigned, parts requests are shipped etc. So by having aggressive sync on, you know that you are always looking at the most up to date data because its constantly syncing.

But can totally appreciate in bad connectivity environments this can cause issues because an aggressive sync will sync more data, more regularly.

One other tip I can give is to ensure you mobile configuration data set doesn't always grow and grow. So ensure that data is only synced while it is relevant, then once its completed, stop syncing it so that over time the data set wont always increase. An example for us is parts requests, they go through these statues: Draft > Open > Shipped > Received > Completed. We only sync the statuses before Completed. If we included completed, then they would never be removed from the data set and it would always increase in size. You can also use last modified dates to help here too, e.g. only sync the not-completed statues OR the last modified date is within the last 7 days, shown here in this screenshot:

Highlighted
Pastry Chef
Pastry Chef

Re: Any recommendations / lessons learned on optimizing the mobile app for the ipad in terms of speed and responsiveness?

Jump to solution

Hi Adam

The problem we saw, and this was a few years ago, so things may have changed, was each time a record was saved it would try to sync, if it could get a connection, even a very slow one (GPRS), it would try to do the sync. This sync could take a very long time, even if it completed, so other syncs would stack up behind it, and in turn these syncs would take a long time, so in effect the iPad was constantly syncing. Often one of these syncs would fail, which could result in a record only being half written (missing data), or the record not getting synced at all (missing records), or the system trying the sync again, not knowing the first attempt had created a record on the server (duplicate records).

Our techs will normally sync at the end of their visit, and all records that have been updated or created, get synced normally without an issue, just using the data sync. We have Set16 set to True, which means only modified data get synced, and this fits with our business model, so any changes made on either the iPad or on the server should get synced, but I’m not sure if this works with aggressive syncs or not.

Great to hear about other user experiences by the way.

Thanks

Russ

Russell JACOBS

Business Analyst (Service)

Phone :

+44 (0)1954 782551

Mobile :

+447966297510

<http://www.domino-everywhere.com/click_redirect.php?url=http%3A%2F%2Fwww.ax-series.com%2F%3Futm_source%3DFooter%26utm_medium%3DEmail%26utm_campaign%3DEmail%252Bfooter%252Blinks&type=hit_extension&id=116>

Please consider your environmental responsibility before printing this e-mail

<http://www.domino-everywhere.com/click_redirect.php?url=http://www.domino-everywhere.com/vcard/Russell_JACOBS.vcf&type=hit_vcard&id=116>

<http://www.domino-everywhere.com/click_redirect.php?url=http://www.domino-printing.com/Global/en/Home.aspx?utm_source=Footer&utm_medium=Email&utm_campaign=Email%2Bfooter%2Btext%2Blinks&type=hit_website&id=116>

<http://www.domino-everywhere.com/click_redirect.php?url=http%3A%2F%2Fwww.youtube.com%2Fuser%2FDominoPrintingUK&type=hit_social&id=116>

<http://www.domino-everywhere.com/click_redirect.php?url=http%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fdomino-uk-limited&type=hit_social&id=116&grouplink=>

<http://www.domino-everywhere.com/click_redirect.php?url=https%3A%2F%2Ftwitter.com%2FDominoDoMoreUK&type=hit_social&id=116>

<http://www.domino-everywhere.com/click_redirect.php?url=http%3A%2F%2Fwww.facebook.com%2FDominoPrinting&type=hit_social&id=116>

<http://www.domino-everywhere.com/click_redirect.php?url=https%3A%2F%2Fplus.google.com%2F%2Bdominoprinting&type=hit_social&id=116>

<http://www.domino-everywhere.com/click_redirect.php?url=http%3A%2F%2Fpinterest.com%2Fdominoprinting%2F&type=hit_social&id=116>

<http://www.domino-everywhere.com/click_redirect.php?url=http%3A%2F%2Fen.wikipedia.org%2Fwiki%2FDomino_Printing_Sciences&type=hit_social&id=116>

0 Likes
Reply