Ping Identity


Traditionally, auditing or controlling access to specifics sites or APIs on a company’s network has required an administrator to type commands into a terminal.

Ping wanted to replace this arcane process with a simple, powerful web application interface that would allow admins to define a site or endpoint, create rules for it, organize those rules into sets, and apply the sets as policies across their network.

Ping Identity


  1. Development
  2. UX Design
  3. Team Integration


  1. Backbone.js
  2. Node.js
  3. Require.js
  4. Bootstrap
  5. SVG icon font
Ping Identity

"I have been showing off the Quick Left developed UI to the executive team to huge excitement and our CEO has declared PingAccess the standard for which our other products should move towards."

Craig Wu, Managing Director, Engineering

Ping Identity

Start small. Move fast. Validate. Iterate.

Ping’s executive team wanted a proof of concept as quickly as possible, well before any of the eventual backend would be complete.  This required a proxy & static server first be built in Node.js to simulate the data the app would be receiving. 

Development then began on a minimal Backbone.js framework, which was presented 8 days into the engagement, successfully demonstrating the core functionality. 

Building on the the framework, a feature-complete MVP was delivered within 6 weeks, giving Ping’s QA team 2 additional weeks to test, while our developers simultaneously addressed bugs, refactored and laid groundwork for future functionality within a new branch, ready to be merged into a subsequent version. 

A Close, Collaborative Partnership

Ping has been a delight to work with, being both hands on and adaptable. After receiving high-level feature requirements, our developers break these into user stories and document on Sprintly.

The client leads can then comment on and accept/reject stories directly, prioritizing each sprint.

All features have been delivered via pull requests and continuous deployment, and their API is exceptionally well-documented using Swagger. As the project has matured, interactions have evolved beyond Google Hangouts & Slack to entail remote pairing, integrating with and training Ping’s engineers on the Backbone front-end.

Prioritizing Good Code & Paying Down Debt

Throughout the project an emphasis has been placed on code visibility, testing, and review. Ping has been generous and enthusiastic about allotting time to refactor and the result is stable software with an exemplary Code Climate score.

On the design side, after a year of work across numerous developers, the application’s interface had grown complex and fractured, and so multiple weeks were committed to design polish, simplifying UI metaphors and applying a uniform navigational language. Usability benefited tremendously.

Like what you see? Then let's get started on your project!

Contact Us