What’s the difference between the mobile ‘Classic’ app and the other one

[Hugh Greenland]

1. What’s the difference between the mobile ‘Classic’ app and the other one?
2. 1. Is the ‘Classic’ app due to be deprecated at any point soon?
   2. Is there a benefit to moving away from the ‘Classic’ app
3. Do any of the mobile apps work with things like Android Auto? We have vehicles with built in screens on the dashboard that runs Android Auto which is used some apps (e.g. waze etc) that display correctly. But the ServiceNow app won't display correctly

[Chuck Tomasi]

The classic app uses HTML largely to render a mobile version of forms and lists. It is a bit limited in that it doesn't provide the native mobile experience that mobile users expect (swiping, accessing camera, geolocation, etc.) It will be around for a while, but not expected to get any enhancements.

In Madrid we delivered a native mobile app for iOS and Android to provide more capabilities. It is a new development paradigm than the older model, and available from within Studio (called Mobile Studio.) For the most part, it's a no/low code experience to develop mobile apps and applets for your organization.

I recommend taking a look at the Agent app (for your fulfillers) and Now Mobile for your employees as part of your mobile strategy. It really does make a huge difference in the adoption of mobile.

As to your final question about Android Auto - no official support from ServiceNow at this point. I love the idea and suggest you put it on the Idea Portal (see the top menu of the community) so others can upvote it. That's where our product managers look for inspiration.

[Chuck Tomasi · Accepted solution]

If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

Thank you