Graphisoft API Developer Site β€” Redesign

A redesign that opens Graphisoft's API site to developers, business partners and beginners. Designed and handed off, not built.

Opening a developer-only API site to business partners and beginners, starting with a home page that asks who you are.

Graphisoft's API developer site had very few users, and it only made sense to people who were already developers. Together with two other designers, I redesigned it for three audiences: developers, business partners and beginners. I designed the home page and the beginner hub, and worked on the user flows, UI and prototypes across the site and the Developer Panel. The project was fully designed and handed off, but it wasn't built: the developers were moved to other priorities.

Year

2023

2023

Role

Product Designer (team of 3) Β· Home page & beginner hub

Product Designer (team of 3) Β· Home page & beginner hub

Work type

Website

Website

Project scope

Information Architecture, User Flows, UI Design, Prototyping, Developer Handoff

Collaboration

Two other product designers, Graphisoft API team, reviewers from outside the project

Context and my role

Graphisoft offers APIs for Archicad (C++ and Python), BIMx, BIMcloud and GDL. Developers use them to build add-ons and integrations. The API site is where they find the SDKs and documentation, request a Developer ID and register their add-ons.

I was one of three product designers on the redesign. I worked on the user flows, UI design and prototypes, and my main focus was the home page and the page for beginners.

πŸ“· IMAGE: Hero image β€” the new home page, full width. Use the version with the rewritten copy.

The problem

The API team told us very few people used the old site. It was hard to navigate, it had no clear path from "what is this?" to "I'm building something", and it only made sense to people who were already developers.

We also wanted more exposure for the APIs. Three groups could benefit, but the old site only spoke to one:

  • Developers who want to build on the API and possibly earn money from their add-ons.

  • Business partners who have an idea and need someone to build it.

  • Beginners who don't know yet what's possible.

πŸ“· IMAGE: Optional β€” a screenshot of the old API site, if you can still get one.

Constraints

  • Build on what exists. To keep development cost low, we reused graphisoft.com components such as the footer, breadcrumbs and carousel.

  • Keep existing accounts and processes. Users sign in with their Graphisoft ID, Developer ID approval stays manual, and add-on management keeps its current logic. We could change the experience, not the back end.

  • The 2023 brand. The design follows Graphisoft's brand from that time. Graphisoft has since changed its visual identity, so these screens don't match today's graphisoft.com.

  • No final content. Copy and contacts weren't ready, so many texts in the design were placeholders.

Process and key decisions

1. Ask who you are before showing what we have

The old site assumed every visitor was a developer. I designed the home page around one question instead: who are you? It has three panels, one per audience: API Developer, API for Business and Learn Archicad API.

At rest, each panel shows only a title and three keywords, so the choice is quick. On hover, the panel opens with a short description of what that audience gets. Visitors can compare the options without reading a wall of text.

πŸ“· IMAGE: Home page at rest and on hover, side by side. A short screen recording of the hover works even better.

2. Audience first, then product

Each panel leads to its own hub. Business partners land on Opportunities, which shows what partners have built and how to get in touch. Beginners land on Archicad Know-How. Developers land on Developer Solutions, which is organized by product (C++ API, Python API, BIMx API, BIMcloud API and GDL), because developers already know which product they want to work with.

This gave the site two levels: the first choice is about who you are, the second about what you're building. Non-developers get a page written for them, and developers get straight to the documentation.

πŸ“· IMAGE: Site map diagram: home page β†’ three hubs β†’ product pages.

πŸ“· IMAGE: The three hubs side by side: Developer Solutions, Opportunities and Archicad Know-How (top section of each).

3. A guided start for beginners

My Learn page became Archicad Know-How. Beginners don't need documentation first; they need a path. The page is built as four steps: define your goals, explore Archicad, start API development, and find inspiration.

Each step asks something concrete, like "What kind of feature do I want to create?" or "What problem will it solve?", and links to a next action, such as downloading a demo version of Archicad or opening the right API page.

πŸ“· IMAGE: Archicad Know-How page β€” the full page, or the first two steps.

4. A Developer Panel that follows the user's stage

Signed-in developers manage everything in the Developer Panel: their Developer ID, add-ons, the Archicad License for Developers and their personal information. These depend on each other. You can't register add-ons or request a license without a Developer ID, and getting one takes a few days of manual approval.

We mapped five stages, from "has a Graphisoft ID only" to "has a Developer ID and a license", and designed every tab for every stage. A tab that isn't available yet explains why and links to the step that unlocks it, instead of showing an empty form. While a Developer ID request is pending, the panel tells users how long it usually takes.

πŸ“· IMAGE: The five-stage user journey (from the User Journey page in Figma).

πŸ“· IMAGE: Add-ons tab in two states: "Please request a Developer ID" and the full add-on table.

5. What changed after the design review

Designers from outside the project reviewed the panel. In the next version, most changes made the panel follow the user's task instead of the company's structure:

  • "User Profile" became "Developer Panel", and the tabs were reordered to follow the process: Developer ID, Add-ons, License, Personal Information.

  • One name for one thing: "Developer License" became "Archicad License for Developers" everywhere, and add-ons are "registered", not "created".

  • Explanations moved into tooltips, so the license page leads with the price and the three request steps.

  • The copy now says why a step matters: without a Developer ID, add-ons only run in the demo version of Archicad.

πŸ“· IMAGE: Before and after: the Developer ID tab in the review version and in version 1.1.

6. A handoff developers could build from

We added notes next to every screen: which graphisoft.com component to reuse, what happens when a user isn't signed in, which fields are required, and where we were open to a simpler technical solution. For example, SDK downloads open in a dialog instead of a separate download page, and the sign-in check only happens when the user clicks download.

πŸ“· IMAGE: A Figma screenshot of one screen with the developer notes next to it. Hide colleagues' names.

Outcome

We finished the design and the handoff: the home page, three hubs, five product pages, and the Developer Panel with every state, plus a clickable prototype and developer notes. The site wasn't built, most likely because the developers were needed for other priorities.

Because it never launched, there's no usage data. If it had shipped, I would have measured how many visitors choose each audience on the home page, how many beginners go on to an API page, and how many Developer ID requests come in.

πŸ“· IMAGE: Optional β€” a short walkthrough video of the clickable prototype.

What I learned

  • Start with who, not what. One question on the home page let us write for three audiences without making developers wade through content meant for beginners.

  • Name things once. Several changes after the review were renames, so one thing has one name everywhere. It's one of the cheapest fixes there is.

  • Placeholder copy hides the design. Generic marketing text made the home page look weaker than it was. For this portfolio, I rewrote it to match what each page actually offers.

next: your team?

Right now

Looking for a mid-senior product design role in B2B SaaS or fintech. Available from December 2026.

Β© 2026 Karola MenyhΓ‘rt Β· Budapest

Built in Framer