Selligy's first product was a mobile app designed for field sales people. It integrated with their calendar, location, and Salesforce to make it easy to prepare for, get to, and report back from sales meetings. At the time we started, Selligy was a team of just 3, so we all had big roles in the product development. I was exclusively responsible for the UX, design, and interactions. Everyone on the team, myself included, also contributed code for the iOS native objective-c app. We also developed an Android version of the app which closely mirrored the design and interactions of our iOS app. For the Android app we built it using web technologies, so I was responsible for all the front-end HTML and CSS used to re-create the app for Android as well.
Selligy Mobile Demo Videos
Selligy Mobile Promotional Video
What Selligy Customers Say
Selligy was featured by Apple in the Business App Store
Selligy Mobile UX
There were quite a few user experience challenges in obscuring a CRM driven workflow behind a mobile interface users would actually want to use. We didn't want our experience to seem like work, but to be as simple and helpful as possible. We wanted to build an experience that would be so great as to break users of old, inefficient habits.
Sign up experience
Mobile users tend to have a short attention span, so for applications that require account set up it's important to simplify it as much as possible to avoid users giving up before they even get into the app. The Selligy app required authentication to a users Salesforce account and the creation of a Selligy account, with optional connections to the users LinkedIn account. We couldn't eliminate the need for Salesforce authentication, but we did minimize the setup process by automatically generating the Selligy user account for them. Their email address was used in conjunction with a generated password, then a token was set on the app so that their login would persist indefinitely. Connecting to other services like LinkedIn was left as a last step, and one they could easily skip.
For the majority of users, there was never a need to log out or change devices. In case they ever did get logged out without knowing their password, we had a clever solution for that: Using a typical password reset email, we included a special button in the email (which appeared only in apple mail) that when clicked from the phone, would open the Selligy app, verify their identity, and give them the option to create a new password. So in the unlikely event they got logged out, they could do the whole password reset in just a matter of taps without leaving their phone.
When to leave to be on time
Years before Siri and Google Now were paying attention to calendar locations, Selligy was scanning them, geo-coding them, and monitoring traffic conditions to give our users an accurate 'time to leave' countdown for their next meeting. If they were running behind, we pre-populated any emails or texts to meeting attendees with a custom message notifying them that the user was late, and even giving an estimated ETA based on their current location and traffic. Anywhere we could, we minimized or eliminated the need to type in Selligy.
Conference calls made easy
One of the worst things people experience on the mobile phones is dialing into conference calls. They require dialing an initial number, then remembering and dialing at least one or two more numbers after connecting. This is difficult when the screen that has the call info disappears as soon as you dial the first number. We created custom algorithms to detect conference call information, and would compose custom dial strings that included delays and subsequent dials for room numbers and such. This allowed our users to dial into conference calls with a single tap. We even gave them the ability to share conference call info in an email, which included a button with a special tel: link that would dial our custom dial string, so other attendees could benefit from one-tap dialing even without the app.