Up42 Console: Enhancement for API Integration

The expansion of UP42’s APIs required a parallel adaptation of the Console to ensure new functionalities (like asset management) were accessible to users. Since the Console is the first touchpoint for new users—and the primary interface for administrators—it was critical to mirror API capabilities in a user-friendly way.

 
 

Why Build It?

  • User Flow: New users interact with the Console before exploring SDKs/APIs.

  • Admin Needs: Business analysis and workspace management rely heavily on the Console.

  • First Iteration Goals:

    • Migrate endpoints from the Storage Service to the Asset Service.

    • Introduce search, sorting, tagging, and reference naming for assets.

    • Allow filtering at account or workspace level.

Solution

Duration: 4-5 weeks | Team: Solo Designer + Dev Collaboration

1. Research & Discovery

  • Conducted 5 customer interviews to identify pain points.

    • Key Insight: Users struggled with disorganized assets—sorting and tagging emerged as top needs.

  • Tech constraints heavily influenced the design approach, meaning our API had many options for variety and features, we had to understand how to best approach this as to not overwhelm the user.

2. Design & Validation

  • Figma Prototypes:

    • Designed sortable tables, tag management, and multi-level filtering.

    • Ensured alignment with the Asset Service migration.

  • Usability Testing:

    • Validated flows with the same users post-interviews.

    • Confirmed tags and reference names significantly improved asset tracking.

3. Handoff & Vision

  • Delivered developer-ready Figma files with annotations.

  • This was the first step in a broader Storage vision—future iterations will expand functionality.

Impact

  • Streamlined Asset Management: Users could now search, tag, and sort assets efficiently.

  • Foundation for Scalability: The Console’s adaptation set the stage for future API-driven features.