Visualizing Tint’s Contract API Attributes

The problem

Customers need to configure and manage validation schemas for their insurance products, but the existing process was cumbersome and prone to errors. Key challenges included:

1. Rigid Schema Management: Editing validation schemas in live environments posed risks, as changes could disrupt customer integrations.
2. Lack of Flexibility: Customers needed to tailor schemas to their specific needs, but the process was not intuitive.
3. Version Control Complexity: Managing multiple versions of schemas across sandbox and production environments was confusing and error-prone.

My approach

Research and Insights

• User Interviews: Conducted interviews with Solution Architects and engineers to understand pain points in schema management.
• Competitive Analysis: Studied how other platforms handle schema validation and version control.
• Usability Testing: Observed users interacting with the existing schema editor to identify friction points.

Key Design Decisions

• Schema Editor Redesign: Created a visual, form-based editor for adding, editing, and removing schema properties.
• Publishing Workflow: Implemented a two-step publishing process (sandbox → production) to reduce risk.

Solution

Validation Schema Editor

The redesigned schema editor provides a clear and intuitive interface for managing schema properties. Key features include:

• Add Property: Users can easily add new properties at the root or nested levels, specifying types and required status.
• Edit Property: Properties can be modified (e.g., marking a field as optional) with a simple toggle.
• Remove Property: Unnecessary properties can be deleted with a confirmation step to prevent accidental removal.

Example Workflow:

• A user adds a reservation_id property (type: string) at the root level.
• They then add a previous_stays property (type: integer) under the pet object.
• Finally, they mark booking_date as optional and remove the amount property.