Experience & AI · LessonBy Sneha I, ServiceNow Trainer, 8 yrs · Published · ServiceNow · all levels
Now Mobile and Mobile Agent
Configure mobile experiences: applets, screens, offline behaviour and push notifications.
Quick answer
Configure mobile experiences: applets, screens, offline behaviour and push notifications.
Key takeaways
- Now Mobile is for employees, Mobile Agent for fulfillers
- Applets are configuration, not native development
- Cut the field count hard for mobile screens
- Test on device with genuine field conditions
Two apps, two audiences
Now Mobile serves employees who request services and check status. Mobile Agent serves fulfillers who work assignments in the field. Both are configured in Studio through mobile applications, launchers and applets rather than by writing native code.
Building screens
Applets bind to a table with a filter, a list layout and a detail screen. Actions on the detail screen let a user update state, add work notes or capture a signature or photo.
Field realities
Mobile design fails when it copies the desktop form.
- Show three or four fields, not thirty
- Use offline capable applets where connectivity is unreliable
- Push notifications need device registration and a working notification policy
- Test on a real device with a real user, simulators hide the problems
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What binds a mobile screen to data?
Frequently asked questions
Can we brand the app?
Yes, colours, logo and launcher content are configurable. The app itself comes from the public stores.
Does it work offline?
Certain applets support offline capture and sync when the device reconnects. Design the process assuming intermittent connectivity.