Archicad Add-on Store — Cards & Resizable Layout

A card system and layout logic for an add-on store inside Archicad, built to work in any window size. Designed, not shipped.

Designing store cards that work with any content and in any window size inside Archicad.

Graphisoft planned an Add-on Store inside Archicad 28: one place where users could browse, install and update the add-ons they're entitled to. I was one of the designers on the project. I owned the store's card system, tag logic, detail page and the layout logic that keeps it working in Archicad's resizable in-app browser window. The project was stopped when another team started building a very similar product in parallel, and neither version shipped.

Year

2024

2024

Role

Product Designer · Cards, tags, detail page, resizable layout

Product Designer · Cards, tags, detail page, resizable layout

Work type

Web App

Web App

Project scope

Component Design, Responsive Layout, UI Design, Interaction Design, Developer Specs

Collaboration

Product designers, Product Owner, developers

Context and my role

Archicad users get add-ons from many places: Graphisoft, partners and third-party developers. There was no single place to find them, check which ones you're entitled to, install them and keep them up to date. The Add-on Store was meant to be that place, built into Archicad's home screen.

The team split the work. I designed the parts every add-on passes through: the cards that show add-ons in the store, the tags on them, the detail page, and the layout rules for every window size.

📷 IMAGE: Hero — the store home screen in grid view, at a typical window size.

The problem

The store had to show very different add-ons in a consistent way. Names, descriptions and the number of tags all varied. And it had to work inside Archicad's built-in browser window, which users can resize freely, from a small window next to their model to a full wide screen.

A card that looks good at one size and with one kind of content breaks at the edges: long names, many tags, a narrow window.

Constraints

  • Inside Archicad, not on the web. The store lives in Archicad's built-in browser. The window is resizable, and opening modal dialogs there is technically difficult.

  • Part of the home screen. The store had to fit into Archicad's home screen, which has its own left-side menu.

  • Limited frontend capacity. Frontend development was the biggest risk on the project, so designs had to be simple to build.

  • Scope for Archicad 28: free Graphisoft and partner add-ons only. No purchases, no browsing from a web browser.

Process and key decisions

1. Start from what Archicad already has

Archicad already had a card system: a senior designer had designed the cards for Project Hub. Before designing new cards, I studied that system: its sizes, its grid and how it responds when the window is resized. I looked at what worked and what didn't, so the store would feel like part of Archicad, not a separate website.

I kept Project Hub's grid system and its resize rules, so the store reflows the same way as the rest of Archicad when users resize the window. I also kept its action button, so installing feels like any other action in Archicad. I changed two things. I made the cards smaller, so users see more add-ons on the first screen, because browsing a store means comparing many options at a glance. And I changed the tag system (see decision 3).

📷 IMAGE: A Project Hub card next to an Add-on Store card.

2. One card family for every window size

The store had to work in a window users resize freely, so one card wasn't enough. I designed a family of cards that share the same structure: grid cards with one-line and two-line names, a smaller card for narrow windows, and a horizontal row for a list view, next to the grid view.

I defined the resize logic: how many columns appear at which width, from the minimum window size up to five columns on wide screens (1792 px and above). Every card variant has a spec: maximum description length (three lines), spacing and layout at the minimum size.

📷 IMAGE: The card family side by side: one-line card, two-line card, small card, list row.

📷 IMAGE: Resize logic: the same page at the minimum window size and at five columns.

3. Tags that don't hide information

Add-ons can have any number of tags. One option was to show a maximum of two tags and replace the rest with a "…" tag. I chose a scrollable tag bar instead, so we never had to limit how many tags an add-on can have.

The bar has three states. At the start, an arrow on the right shows there's more. In the middle, arrows appear on both sides. At the end, the arrow moves to the left. When the tags fit, there are no arrows at all.

✏️ TO DO: Add why it was important that all tags are reachable on the card, not only on the detail page.

📷 IMAGE: The tag bar in its three scroll states, plus the "tags fit" state.

4. A detail page for everything the card can't hold

The card answers "what is this?". The detail page answers "should I install it?". It holds the full description and all tags, plus version, file size, compatibility, publish date, and links to the publisher's support page and website.

Some things were deliberately left out. After a review, we removed download counts and ratings, because the store wouldn't have that data at launch, and breadcrumbs, because the store has so few levels that a back arrow is enough. We also decided that whether an add-on is available to you only needs to show on the detail page, not on every card.

✏️ TO DO: Add the hardest decision on the detail page, and mark which of these decisions were yours.

📷 IMAGE: The detail page.

5. Working with critique

The design reviews were direct. Feedback included "you're working from assumptions" and "decide, don't keep so many directions open". In response, the team narrowed the directions, showed the same features on every variant so they could be compared fairly, and removed a side menu that would have clashed with Archicad's home screen.

✏️ TO DO: Add how this feedback changed your own parts.

📷 IMAGE: Optional — an early lo-fi wireframe next to the final design.

Outcome

I delivered the card family for grid and list views, the tag logic, the detail page, the resize logic for every window size and a specification for developers. The project was stopped when another team started building a very similar product in parallel, and neither version shipped. There's no usage data to report.

📷 IMAGE: Optional — one spec frame, to show the developer handoff.

What I learned

✏️ TO DO: Keep only the points that are true for you.

  • Build on what the product already has. Studying Project Hub's cards first meant the store could feel like part of Archicad, and I didn't have to solve problems that were already solved.

  • Design components for the extremes. The longest name, the most tags and the narrowest window decide whether a card works. The average case almost always does.

  • Narrow directions earlier. Keeping many options open felt safe, but it made reviews harder. Now I name the decision each variant is meant to settle.

  • Ask early who else is working on the same problem. Not something a designer controls alone, but a question worth asking at the start of any project.

← all work

Graphisoft · Archicad 28 · In-app store

Archicad Add-on Store

One card system for every add-on, in any window size.

What

A store inside Archicad's home screen where users could find and download the add-ons they're entitled to, from one catalog.

My part

The card system, the tag logic, the detail page and the layout rules that keep the store working in Archicad's resizable in-app browser.

Result

Designed and specified for developers. The project was stopped when another team started a very similar product in parallel, and neither version shipped.

Role

Product Designer

Team

2 designers, each owning part of the store

Year

2024

Scope

Card systemResponsive layoutDesign specsUnreleased

01 — context

One place for every add-on

Archicad users get add-ons from Graphisoft, partners and third-party developers. There was no single place to find them, see which ones you're entitled to and download them. The Add-on Store was meant to be that place, built into Archicad's home screen.

We were two designers on the project, and we split the work. I designed the parts every add-on passes through: the cards, the tags on them, the detail page and the layout rules for every window size.

02 — the problem

Different content, any window size

The store had to show very different add-ons in a consistent way, inside a window users resize freely. A card that looks good at one size with one kind of content breaks at the edges: long names, many tags, a narrow window.

Inside Archicad

The store runs in Archicad's built-in browser. The window is resizable, and modal dialogs are technically hard to open there.

Part of the home screen

It had to fit next to the home screen's own left-side menu.

Limited frontend capacity

Frontend development was the biggest risk on the project, so every design had to be simple to build.

Scope for Archicad 28

Free Graphisoft and partner add-ons only. No purchases, no browsing from a web browser.

03 — key decisions

Build on Archicad, design for the edges

a

A catalog, not one-click install

Our first plan was one-click install: add-ons that download and work right away. That was a huge amount of development work, made complicated by the limits of a legacy system and by who is entitled to what. About halfway through the project, we found that on every forum, users only asked for one catalog where they can see all add-ons, instead of collecting them from many different websites. Installing them and putting them in the right folders by hand wasn't a problem for them. So we dropped one-click install and went on with the catalog.

one-click installone catalog for every add-on
b

Start from what Archicad already has

A senior designer had already designed the cards for Project Hub. Before drawing anything new, I studied that system: its sizes, its grid and how it reacts when the window is resized. I kept the grid, the resize rules and the action button, so the store reflows like the rest of Archicad and the main action feels like any other action in Archicad.

Project Hub cardsmaller store cardso more add-ons fit on the first screen
A Project Hub card next to the Add-on Store card. Same grid and action button, smaller card. The cards still show the early Install button; the final design used Download.

A Project Hub card next to the Add-on Store card. Same grid and action button, smaller card. The cards still show the early Install button; the final design used Download.

a

One card family, not one card

One card wasn't enough for a window that goes from a small panel next to the model to a full wide screen. I designed a family with the same structure: grid cards with one-line and two-line names, a smaller card for narrow windows, and a horizontal row for the list view.

b

Rules for every width

I defined how many columns appear at which width, and gave every variant a spec: a maximum of three lines of description, spacing, and layout at the minimum window size.

5

columns at most, from the minimum window size up to 1792 px and wider.

The same page at the minimum window size and at five columns.

The same page at the minimum window size and at five columns.

a

Tags that don't hide information

Tags help users filter visually: they scan the cards and spot the add-ons relevant to them. Hiding tags behind a "…" tag would have broken that. Localization made it harder: in German, every tag is much longer, so a solution that only works in English wasn't enough. I designed a scrollable tag bar instead. It works for any number and length of tags, and the arrows show users that more tags are available: on the right at the start, on both sides in the middle, on the left at the end. When the tags fit, there are no arrows.

two tags + "…"a scrollable tag bar
The tag bar when the tags fit, and in its three scroll states.

The tag bar when the tags fit, and in its three scroll states.

a

A detail page for what the card can't hold

The card answers "what is this?". The detail page answers "should I download it?": full description, all tags, version, file size, compatibility, publish date, and links to the publisher's support page and website. I left out download counts and ratings. Developers couldn't have built a rating system in time, and it wasn't needed in this context: users install add-ons they're already entitled to, so I didn't want to copy an app store. We also dropped breadcrumbs, because a back arrow was enough for so few levels. Whether an add-on is available to you shows only on the detail page, not on every card.

app store patternsonly what helps you decide
The detail page: the full description, all tags, and the facts you need before downloading.

The detail page: the full description, all tags, and the facts you need before downloading.

04 — the result

Ready for development, never shipped

I delivered the card family for grid and list views, the tag logic, the detail page, the resize logic for every window size and a specification for developers. The project was stopped when another team started building a very similar product in parallel, and neither version shipped, so there's no usage data to report.

05 — what I learned

Solve the problem users actually have

Check what users are asking for

We spent half the project on one-click install, a problem nobody had asked us to solve. A much simpler catalog covered exactly what users needed. What users already ask for should decide how big the solution is.

Build on what the product already has

Studying Project Hub first meant the store felt like part of Archicad, and I didn't re-solve problems that were already solved.

Design for the extremes

The longest name, the most tags and the narrowest window decide whether a card works. The average case almost always does.

Narrow directions earlier

Keeping many options open felt safe, but it made reviews harder. Now I name the decision each variant is meant to settle.

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