Posted by Samuel Prasad on Apr 22, 2019 7:00 am
Craig and Joseph,
Thank you for the responses.
I understand that communities are different. And, yes content is different. But, the types of content are the same - events, discussions, news, resources, etc. And that precisely must be the reason for developing the myASQ app, which will not only make the user experience richer, but also result in increased participation. Let's not forget that we live in a time when most Internet access happens from smartphones and mobile devices.
Here's my thinking on a myASQ app user's experience - when the app is launched and if the user chooses to authenticate, then content relevant to the user's community will be displayed in a format that allows for easy consumption and interaction from a mobile device. In case of members who do not belong to a community (non-members) or members who choose not to authenticate, general content available to the public at large can be displayed with information on benefits of membership. The app will allow ASQ to push notifications (with alerts) non-intrusively without flooding the email inbox of both members and non-members who have opted in. Options to personalize can also be provided at a later stage so that the user is able to customize the landing page.
I encourage ASQ to adopt a mobile-first strategy and not make desk-top deployments their primary focus.
Regards,
Sam
Samuel Prasad, PhD, CSQE