Slash GraphQL - Design Principles

Photo by Max McKinnon on Unsplash

Our passion for user experience

Creating an incredible user experience is a fundamental core value at Dgraph. This holds true for our latest product offering — Slash GraphQL. Slash GraphQL is a fully-managed GraphQL backend database service that lets you focus on building apps, not managing infrastructure. Building Slash required a design process that focused on creating the right user experience to realize this vision.

Our design principles -

  1. Direction over choice. We want developers to focus on app development and guide them on a success path, rather than asking them to spend time navigating a labyrinth of choices to configure and manage Slash. Fewer clicks for the app developer means more work for us during Slash design, but less work for you, the app developer.
  2. Enable super users. Our users are developers — who love keyboard shortcuts and keyboard-based navigation, and who love to become power-users with any tool they use in their workflow. Accessibility for all developers is important, as is helping you to supercharge your workflow.
  3. Build purposeful interfaces. We want interfaces to resemble similar patterns and speak to the actions developers want to perform. Every piece of the screen needs to match user intent and help the user to take action.
  4. Build “toy-like” (indestructible) interactions. Developers are smart, fast-moving, and results-oriented. We need to ensure that each interaction is reliable, make sure that error handling is robust, and make sure that error messages are clear and actionable. We imagine that we are building a toy for a baby — it should have no sharp edges or small parts that can easily break off and be swallowed.

Originally published at

Frontend at DgraphLabs