OOP as State Management: What Svelte 5 Runes Made Obvious
How Svelte 5 runes turn plain TypeScript classes into reactive stores, replacing Redux ceremony with object-oriented simplicity.
I build the kind of web application most frontend developers never touch: interactive canvas, annotation and map interfaces over very large datasets.
Focused on creating intuitive and performant web experiences. Bridging the gap between design and development.

How Svelte 5 runes turn plain TypeScript classes into reactive stores, replacing Redux ceremony with object-oriented simplicity.
Why "what if Svelte dies?" is the wrong question: your domain logic outlives any framework, and Svelte 5 runes remove the state management ceremony.
Migrating a CRM from Next.js and Redux to SvelteKit 5: file-based layouts, load functions as built-in state, idiomatic stores and no more provider hell.
Redux Toolkit in a Next.js app: reducers vs extraReducers, createSlice and createAsyncThunk, RTK vs Context, and pairing Redux with server actions.
Lessons from building a canvas annotation app with React, Redux and Konva: state as the source of truth, event handling as translation, and performance.
I work on a national-scale map application for public transport analysis, where we moved from ArcGIS to OpenLayers. Before that, through Capgemini, I developed STID Annotation for Equinor, the application engineers use to annotate technical documentation across Equinor installations.
Before Norway, I founded and ran a video production and web agency in Serbia for eight years. Today I work across the stack, from Norway, and write here about architecture and state management.