NWS Mobile- Beta Testing

[dvdgarofalo]

For those who are currently using/testing the NWS Mobile: How is your experience going? What kinds of issues have you faced? Have you implemented it for the entire share group? Any other observations please share. TYIA

[foghorn]

On 2/8/2026 at 7:42 AM, dvdgarofalo said:

How is your experience going?

Just activated yesterday. Installed on a high-end Samsung Android tablet.

• Install: Had trouble finding NW Scheduler on Google Play Store - had to spell it out completely for some reason
• Activation: simple enough, but notice they now send you a one-time activation code to your email. 
• Normal Startup: Time to sync with congregation data is about same as desktop
• User Interface: Different from Desktop, of course. But very simple and intuitive
• Responsiveness: VERY quick - seems faster than desktop for displaying data
• Usefulness - only 
• Data updating: haven't tried any yet.

[pasher123]

Since we have started using the NWS Mobile, many of the friends have been disconnected from the NW Publisher app. Their name and personal pin are correct, but they receive the following error message "Sorry, this information does not match anyone in this congregation. Please try again or try using CAPITAL LETTERS when entering your First name, or contact your local elders, or tap Help". 

[-Chris-]

• Installed and linked fine on my iPhone.
• UI issues pasting various codes and passwords in on the iPad. I watched another brother type those in without any issue at all on his iPad, was a copy and paste issue. Felt like a problem in whatever UI framework they're using, could make progress by rotating the screen.
• NWS Mobile displays incorrect PINs for publishers, apparently two leading '0' for older 6 digit PINs. These won't work in Publisher.
• A Life and Ministry assignment made on NWS Mobile only partially synced with desktop Scheduler well after the assignment was made. Name field was blank on desktop but Chairman Outline and NWS Publisher showed the brother scheduled. No update at the time for Scheduler. Restart a couple of times resolved it.