You open a new tab to look something up. A headline catches your eye. You take a quick look, save it for later, and go back to what you were doing.
I've always liked that idea behind daily.dev's browser extension. I had it set as my default new-tab page, and the idea stayed with me: discovering something interesting shouldn't always require a deliberate visit to a website.
When I wanted to see what was happening here, I'd open DEV and check the feed. That's a small step, but it means I have to remember to do it. A new tab is already part of my day.
So I built DEV New Tab, an unofficial Chrome extension that puts the DEV community there.
Open a new tab and you can browse DEV articles, see who's writing them, and find something worth opening.
The extension has For you, Following, Latest, Top, and Curated feeds. You can use a grid or a list, switch themes, add your own shortcuts, and keep useful articles close with bookmarks or local saves.
Clicking a card opens a preview. The original article is always one click away on DEV, along with its comments and the author's profile.
That was the experience I wanted: a post gets a chance to catch my attention before I start typing another URL.
While building this, Hacktoberfest got me thinking about what else I could try. Google's built-in AI APIs in Chrome were especially interesting.
Could the browser itself help me decide whether a long article was worth opening?
I used Chrome's local Prompt API to generate a short overview from the public article text. On supported setups, the model runs on your device. You don't need to add an AI API key, and the extension doesn't send the article to a publisher-operated AI server.
Browser, hardware, and language support vary. If local AI isn't available, you can still browse the feed and open the original articles.
The overview is there to help you get your bearings. It's AI-generated, so the original is still the place to check the details.
You can prepare a few visible articles ahead of time, wait until you open one, or opt into preparing all the articles already loaded in the feed. Cached overviews are reused. Opening and closing a preview doesn't restart a job that's already running.
Some of the fiddly work was around that last part. A summary finishing shouldn't move neighboring cards around. An author bio arriving shouldn't push the sharing buttons down. Those little things matter when this is a page you'll open repeatedly.
Select part of an overview and a small toolbar appears. You can copy just the text, copy it with the article's source, or save it as a snapshot card.
The snapshots include the article title, author, and source link, with readable highlighted text in DEV-inspired colors. You can export the full overview from the menu too.
I want the author and original post to stay attached to the thing being shared. If a passage makes someone curious, they should be able to find the article behind it.