Currently Technical Director at Blink d.o.o.
I take on collaborations through Blink d.o.o., building products from the first sketch to production. Every pixel on studioblink.ba is my work — design and development. Most recently Urbano, a civic platform for a city of 180,000: a RAG assistant grounded in 22,300 city documents, 143 government forms, five surfaces, one account.
Selected works BLink case studies
The need for creation, curiosity, the need to understand the world around me, and a thirst for new knowledge—which from the earliest years found their most fertile ground in software, and informatics and computing in general.
At twelve years old began my daily journey through code and computer systems—from microprocessor architecture to the sophisticated levels of abstraction that characterize application software today.
After more than a decade of practical engagement with computers, and almost a decade of writing software, today I can present my technical knowledge as the result of years of consistent dedication to every aspect of software development—from basic logic and understanding hardware limitations to complex architectures of distributed systems.
What emerges is less a collection of skills than a way of working. The same attention that goes into debugging a production incident goes into shaping a reusable abstraction, or refactoring an old module to match a cleaner mental model. The job is never merely to ship—it is to leave behind code that the next engineer will want to read, and systems that continue to explain themselves long after the original author has moved on.
"I see myself as homo poeticus who seeks creative synthesis through all aspects of work.
All of this converges, or rather: all of this is the convergence. The code I write carries the same aesthetic demand as the sentence I construct. The architecture of a distributed system mirrors the architecture of an argument. There is no separation between technical and humanistic—that distinction belongs to an era of specialization I refuse to inherit.
The literary tradition that shaped my thinking runs through the French moralists and Russian maximalists in equal measure—André Gide's acte gratuit and the liberation of authentic action, Proust's obsessive archaeology of memory and time, Dostoevsky's unflinching descent into the cellars of human psychology where logic dissolves into paradox.
Philosophy functions here not as academic credential but as operational framework. Kierkegaard's leap remains the founding gesture—the recognition that at some point analysis must yield to commitment, that infinite reflection is paralysis dressed in sophistication.
Philosophy gives you the questions. Engineering demands the answers. Between the thinking and the building lives the work that matters — late nights, broken deploys, elegant solutions, and the slow accumulation of craft.
Seven roles, two acts — engineering, and the craft around it.
Logic, structure,
the long refinement.
After more than a decade of practical engagement with computers, and almost a decade of writing software, I can present my technical knowledge as the result of years of consistent dedication to every aspect of software development — from basic logic and hardware limitations to the complex architecture of distributed systems.
My starting point was a simple fascination with creating something from nothing using code; over time it became a professional orientation in which I mastered almost every segment of modern software development.
Already at twelve I built my first static web pages — a field of experimentation, but also an introduction to systematic, structured thinking. As my interest grew, focus shifted to dynamic systems, where I began developing my own frontend applications, paying special attention to interface, experience and accessibility.
Soon after, backend logic became the natural next step: building APIs, implementing business logic, and solving the problems that appear when applications must talk to databases, manage users, respect security and scale. What shaped me most was going through every phase independently — idea, design, implementation, testing, deployment, optimization — which forced me to understand how each layer works and how they coexist.
Over time I built solutions that resist simple patterns — web portals for news agencies, e-commerce with complex inventory and payment logic, internal analytics tools, and services drawing on many APIs: financial, crypto markets, health standards. Connecting that many sources and interfaces meant constantly minding performance, security and scalability.
In recent years I have focused intensively on mobile, with Expo and React Native at the core — not extended web interfaces but independent products using geolocation, offline capability, authentication, push notifications and the camera, with a deep grasp of the whole ecosystem, from state and local databases to UI performance and store distribution.
Authentication and security hold a special place: I have always built my own login systems rather than settle for ready-made libraries, designing flows for every scenario — multiple devices, automatic token renewal, abuse protection, identity verification — tested on real users in production.
My deepest competency is broader architecture — systems that grow and live for years without falling when users multiply tenfold. One result I am proud of: verifying authentic physical locations without the Google Places API (now largely withdrawn from open use), by combining web scraping, AI analysis, local heuristics and many public and closed sources.
A special focus is the practical application of AI. Within my startup I built an AI assistant that personalizes the experience through contextual content — connecting people with events, places and points of interest by behavior, location and interest — combining data analysis, semantic processing, geolocation and vector search. The work spans LLM integration through APIs and retrieval-augmented generation: embedding models, vector databases and proprietary filtering to search by meaning, not form.
I am comfortable building the interface logic that talks to LLMs — conversational flows, fallback mechanisms, relevance evaluation — for real control over AI behavior. And beyond practice: during my software-engineering studies I chose electives in machine learning, statistical modeling and AI for a deeper mathematical foundation.
Whatever the web needs — built on Next.js and Nuxt over Strapi and Drizzle, one typed codebase from database to DOM.
One React Native codebase on Expo, shipped to both stores — typed, with live data and encrypted messaging.
Typed Node services over Postgres — REST and WebSocket, encryption, and the schemas everything else is built on.
Turborepo monorepos through Docker and CI to AWS, GCP and Cloudflare — typed configs, deploys gated on lint, types and tests.
Project manager, designer, art director.
Roadmaps, scope and milestones across five products — one person holding the plan from first ticket to release.
Editorial type, motion and interface systems in Figma — then built in code, not handed off.
One visual language across the whole product — type, colour, rhythm, restraint — set once and held on every screen.
Make a thing. Then make it again, better.
I started BLink with Petar Kremenović because the city we live in still needed building — a digitized public-transit system, a civic platform that closes the loop, ride-hailing tuned to a local market. A smart-city stack, plus founder tools nobody else was building. So we started a startup.
Co-founder & Technical Director
Petar Kremenović and I started Blink in December 2025 and registered Blink d.o.o. in 2026. I lead the technical work and take on collaborations through the studio.
Everything you see on studioblink.ba is my work — design, development, every single pixel.
Explore studioblink.ba
Alongside client work, we build our own products. Every venture brings design, engineering and product thinking into the same studio.
A digital front door to the city: citizen reports, maps, municipal services and a grounded AI assistant.
One connected practice: appointments, clinical records, patient portals, billing and the clinic dashboard.
Routes, timetables and live bus arrivals for Banja Luka, designed around the everyday commuter.
In developmentA local ride platform connecting passengers and drivers, with clear fares and cash or card payments.
In developmentAn AI workspace for running a company: deploys, project updates and recurring weekly reviews.
In developmentA product photography studio that turns catalogue items into consistent images and campaign formats.
An AI phone assistant for clinics, handling calls, appointments and useful conversation summaries.
A photographic archive workspace for visual search, AI classification, curated collections and portfolio publishing.
A contribution graph is just colored squares — until you read it as a calendar. Each square is a day something got built, fixed, or broken and rebuilt. The interesting part is not the streaks but the gaps — the weeks spent reading, rethinking, or simply living. Consistency is not about never stopping. It is about always returning.
Years of commits, experiments and shipped systems compressed into one field of work.
Before the first function, there was a sentence. Dostoevsky taught that reason has limits. Kierkegaard, that the leap is the only honest move. Proust, that attention is the rarest form of generosity. Every book left a residue — not knowledge, but posture. The way you hold a problem. The patience before the elegant solution. Code is written in languages, but thinking is shaped by literature.
The eye learns before the hand. Every interface begins as a gaze — a fraction of a second where the visitor decides: stay or leave. Beauty is not ornament. It is the shortest path to trust.
Off the clock — the screen after midnight, golden hour on film, and the quiet hours in between.
Quiet correspondence preferred. For anything urgent — a voice call cuts through faster than a thread.
Thereisacrackineverything
That’showthelightgetsin
Thank you
for sticking to the end.
scroll on — return to I, opening frame follows
