A means of direct communication between workers and employers using Snag’s (formerly Snagajob) Small Business SaaS product codenamed ‘GO’.
Received a single page requirements document focused on user engagement and communication between workers (seekers who have been hired by an employer using the Snagajob GO product) and managers for daily communication. This network of workers and employers also initially required social networking features to grow the product adoption user base. The messaging API for this feature was provided by Layer, a communication and messaging platform developer.
The Snagajob SMB GO Product was a set of small business management tools for recruiting and scheduling employees. GO’s target market are small business with less than 100 hourly employees. At the time of development of this product feature, the Go product was in a pre-launch status.
Product Launched in the Android App on Aug 18th, 2017 on both iOS and Android apps.
The messaging feature has been deployed to production apps on the android and iOS devices as of Q4 2017, and on the GO Employer product in Q1 2018 to about 10 clients who have activated the messaging service.
Access to the messaging feature is by logged in user on iOS & Android client apps, with activated invitation via push/SMS notification from the employer GO product dashboard.
Understanding product requirements
Leveraging feature requirements from product owners, developed task flows and hand drawn wireframes to verify pattern conflicts with existing app features.
Defining a minimum viable UX feature
After finalizing the UX flow based on the product requirements and iterative discussions with product, engineering and design management, an reduced minimum feature UX flow was presented to the team. This was the basis for scoping the messaging feature release.
Preparing feature for production
Once the UX flow for messaging was finalized for engineering on the Android client, the process of applying the brand and UI polish to the wireframes resulted in this set of screens for formalizing the design spec, which where then exported to zeppelin.io to reduce the time of style guide production and asset delivery.