Fityra/Blog
ArticlesBuild in PublicDeep Divesfityra.app ↗
Fityra/Blog

Technical deep dives and lessons learned building the Fityra ecosystem.

RSSSitemap

Blog

  • All Articles
  • Build in Public
  • Technical Deep Dives
  • Product Updates

Ecosystem

  • fityra.app ↗
  • SaaSLift ↗
  • Extensions ↗

© 2026 Edson Mark. All rights reserved.

Shipping fast. Writing everything down.

Technical deep dives, product updates, and lessons learned building the Fityra ecosystem — from API design to Chrome extensions to SaaS launches.

Browse all articlesSubscribe via RSS

Featured · Chrome Extensions

How I Built Extension Permission Monitor

The build story behind Extension Permission Monitor: reading installed extensions with chrome.management, translating permissions, designing risk cues, and shipping a calmer privacy tool.

Read post
How I Built Extension Permission Monitor

Featured · AI and LLM

The New Developer Skill Is Verification, Not Typing Faster

AI can generate code quickly, but the developer who verifies behavior, security, and product fit is the one who actually ships safely.

Read post
The New Developer Skill Is Verification, Not Typing Faster

Featured · AI and LLM

The Real Workflow of a Solo Developer Using AI Agents

A practical solo developer workflow for using AI agents without losing judgment, quality, or control of the final product.

Read post
The Real Workflow of a Solo Developer Using AI Agents

Recent articles

Latest from the blog

All articles
Browsing in bursts? Your history should group itself like you do.
Chrome Extensionsbrowser memorybrowsing sessions

Browsing in bursts? Your history should group itself like you do.

Browsing in bursts? Your history should group itself like you do. I do not browse in a straight line. I doubt most people do. I browse in bursts. A burst of research before building a feature. A burst of comparison before choosing a tool. A burst of debugging when something breaks. A burst of reading when one article...

5 min readRead more
I replaced chrome://history — here's why I skipped the AI everyone else would've reached for
Chrome Extensionsbrowser memorychrome history replacement

I replaced chrome://history — here's why I skipped the AI everyone else would've reached for

I replaced chrome://history — here's why I skipped the AI everyone else would've reached for If you tell someone you are building a smarter browser history page, the AI idea arrives almost immediately. Summarize my tabs. Ask my history questions. Name my sessions. Turn yesterday's browsing into a neat report. It is an...

5 min readRead more
Local-first, deterministic, and still smarter than chrome://history
Chrome Extensionsbrowser memorylocal-first

Local-first, deterministic, and still smarter than chrome://history

Local first, deterministic, and still smarter than chrome://history I like tools that are boring in the right places. That might sound like a strange way to describe a browser history replacement, but it is exactly how I think about Browser Memory. The product should feel useful. It should help me return to sessions,...

6 min readRead more
What if Chrome's history page understood sessions?
Chrome Extensionsbrowser memorychrome history

What if Chrome's history page understood sessions?

What if Chrome's history page understood sessions? I kept asking myself one question while building Browser Memory: What if Chrome's history page understood sessions? Not in a complicated way. Not as a full productivity dashboard. Just enough to know that the seven pages I opened while debugging one problem belonged...

5 min readRead more
No AI, no cloud, no account: rethinking what smart means in a browser extension
Chrome Extensionsbrowser memoryno ai

No AI, no cloud, no account: rethinking what smart means in a browser extension

No AI, no cloud, no account: rethinking what smart means in a browser extension When I started building Browser Memory, I kept running into the same assumption: If a browser extension organizes your history, it should probably use AI. I get why that idea appears so quickly. Browser history is full of context. A model...

6 min readRead more
I stopped re-Googling things I'd already found — here's what I built instead
Chrome Extensionsbrowser memorychrome history

I stopped re-Googling things I'd already found — here's what I built instead

I stopped re Googling things I'd already found — here's what I built instead There is a special kind of frustration in searching for something you already found. Not something similar. Not a replacement. The exact page. You remember seeing it. You remember it helped. You might even remember what you were working on...

6 min readRead more

Popular topics

chrome extensions14solo developer13privacy11browser memory10local-first10chrome extension10browser productivity9chrome history7color scheme extractor7web design7extension permission monitor7build in public6browser security6color palette5design tokens5extension permissions5fityra5research workflow4no ai4landing pages4

Stay in the loop

New articles, product updates, and build-in-public progress. No spam — unsubscribe any time.

Subscribe via RSS