Work / Entry

Sameieportalen

A self-initiated portal concept for small Norwegian housing associations, bringing shared information, tasks, documents and decisions into one clearer space.

Concept · Product direction · UX/UI
Product concept, information architecture, resident and administrator flows, interface design and prototype direction.
Lovable · GitHub · AI-assisted implementation · Pilot development
SameieportalenFrame / 001
Introduction

Sameieportalen started with a practical need in my own four-unit housing association in Oslo: one place for the information, decisions and responsibilities we share. The product is aimed at small, resident-run communities that otherwise rely on email, spreadsheets and document folders.

I am developing a public association website and a private resident portal around three everyday needs: my home, our shared finances and what happens next. My work covers product direction, information architecture, UX/UI and iterative prototyping, with AI-assisted implementation through Lovable and GitHub.

Since the first prototype, development has expanded into documented cost allocation, account and loan overviews, forum discussions, meeting protocols and connected document history. Norwegian, Swedish and English are supported across the public journey and shared portal views; some detailed administration forms remain Norwegian. Registration currently serves Norwegian owner associations.

This remains a product in development for a planned four-unit pilot. The separate read-only demo uses fictional people and amounts. Implemented functionality and technical checks are progress toward that pilot, not evidence of customer adoption or measured user impact.

01 — Start with the resident

The portal is organised around a resident’s home and responsibilities. “Min bolig” brings unit information, relevant documents and costs together, while tasks, dates and recent events give residents a practical starting point.

The design aims to keep everyday information easy to reach on a phone, with a clear distinction between shared association information and details belonging to an individual unit.

02 — Make shared responsibilities understandable

Shared finances need an explanation, not just a total. Development now includes cost registration with a preview of each unit’s allocation, documented distribution keys, savings accounts, recorded movements and loan overviews. Historical allocations are retained when the underlying basis changes. Confirmed balances and forecasts remain separate, and corrections preserve the original record.

Forum discussions can lead to a case and follow-up task. Meeting protocols support electronic confirmation, locking and PDF archiving, linking decisions to their documents and history. Advisory polls are distinguished from formal meeting votes; electronic confirmation is not presented as verified e-signing.

The central design choice is traceability: residents should be able to see what a figure or decision is based on and what happens next. The portal provides information and administration, without connecting to bank accounts or executing payments.

03 — A working prototype, with testing ahead

Development update — 27 October 2026. The project has progressed beyond the first interface prototype into connected resident and administrator workflows. Project verification reports cover cost allocation, documents, forum access, meeting protocols and role boundaries in isolated test associations. These checks do not replace testing with the pilot’s residents or prove that every development change is live.

Norwegian, Swedish and English are available across the public journey and shared portal views. Detailed administration forms still contain Norwegian text, and the registration model currently targets Norwegian owner associations. Broader Swedish support is a product direction, not a completed local legal model.

Next: verify the release and invitation journey, test real everyday tasks with the planned four-unit pilot, and refine the interface from observed difficulties. Analytics and private product feedback are separate development work and are not presented here as released features. The read-only demo uses fictional data; the cover image shows the earlier product-page prototype. No customer adoption or measured user outcomes are claimed.