HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
plateaukao
einkbro
Kotlin2021–2026
plateaukao / einkbro

einkbro

A small, fast web browser based on Android WebView. It's tailored for E-Ink devices but also works great on normal android devices.

8Distinct people
21Mentions
0Explicit recommenders
2.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A small, fast web browser based on Android WebView. It's tailored for E-Ink devices but also works great on normal android devices.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year21 dated mentions

Observed mentions: 2021-04-20 04:45:20 UTC to 2026-08-10 23:08:29 UTC.

0123452021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC422
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC514
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

4 sources
I'm a huge fan of Readability Mode and use it often. It's proof that Web design isn't the solution, Web design is the problem. For those who are using e-ink devices, or even just standard tablets, EInkBro is another immensely useful tool. Yes, it's a standalone browser, not a mode on Firefox, Safari, Vivalti, etc. https://github.com/plateaukao/browser (Available through Google Play, F-Droid and other sources. Android-only, sorry iOS fans.) What it offers over standard browsers is that it's optimised for e-ink displays. That is, it favours pagination over scrolling, runs to full-screen, can easily adjust font size up or down (no more itsy-bitsy-teen-weenie-yellow-polka-dot HN fonts), bold text, and has its own reader mode as well. Even on a standard tablet, some of these features are a huge step above and beyond the mainstream browsers
Read the rest
. The feature-set is limited, some of the UI is a bit rough, and a few things are just plain broken (if you need to edit entries in the JS or Cookie enabled/disabled sites ... you have to delete all data and start over again). That said, my usage is evolving from sending individual pages to EInkBrow when I want to do long-form reading, to using it at least part-time as a primary browser. (Mozilla Fennec Fox is my first choice, still.) The browser is stable and very much usable despite this. The developer is responsive to requests and bug reports. What's most refreshing is that the design principle is readability of Web content, as determined by the user, and not by the page author or publisher.
In The most underused browser feature: reader mode
Long sympathetic with the Jacob Nielsen / PDF bad camp ... I've had some recent changes of heart. Not a full convert, but PDF is often superior to HTML, especially for longer-form and complex noninteractive content. Books are an artefact whose design has evolved over the centuries to accommodate human-scale ergonomics: font size, paper and ink colour, words per line, lines per page, pages per volume, overall weight and dimensions. Standard-sized books are all larger than the largest current mobile phones, with diagonal measures of about 9--12 inches. There are smaller and larger books, but those are compromises either to portability (pocketbooks) or to large-format resolution and detail ("coffee table" books, atlases, and the like). Magazines tend to run even larger (about 13"), broadsheet newspapers larger yet. Most criticisms of P
Read the rest
DFs are actually criticisms of the devices and displays used to read them. Poor resolution, incorrect aspect ratios, and small display sizes (especially mobile devices) are the key problems. Reading PDFs on a tablet, especially a larger e-ink device, is a game-changer. I now actively avoid HTML, or at least launch it in a browser designed with e-ink in mind (EInkBro: https://github.com/plateaukao/browser). Otherwise, my large (13.3") high-DPI (200+) B&W ebook reader is an excellent long-form immersive reading tool. The key requirement of a mobile phone is that it fit in a pocket, handbag, or purse. They are too small for reading, and aren't designed for that purpose. Current devices feature screen sizes of roughly 5--7 inches (diagonal measurement). At the lower end, that's smaller than a 3x5 index card (6"), and the largest barely the size of a 4x6 card (7"). On desktops, the first display that offered what I felt was a truly comfortable two-pages-up PDF reading experience was the 27" Retina iMac. Its 5K display (itself an oddball size) suits document work well. Even not fully maximised, most books are highly readable (leaving screen space for other tasks), and at full maximisation, details really stand out especially from scans of historical editions. (Such details aren't always relevent, but often are.) PDF also provides capabilities HTML either cannot or does not by default (and few seem to be persuaded to offer), especially pagination, formulae, and a spatially-persistent layout (if you have a spatial memory, this is very valuable). PDFs can though often do not include internal navigation (chapters, sections, etc.), search (if full text is included), and most critically, metadata (at a minimum, author, title, date, and publisher, see the full Dublin Core metadata specification for what should be required). PDFs can also be published directly to device sizes (or to a set of form factors encompassing typical devices), as several others note. Some of the issues aren't entirely intrinsic, and my feeling is that wider use of PDFs for online content would lead to a proliferation of PDF annoyances to match present-day Web annoyances. In each case, the fundamental problem is that publishers rather than readers have final say over presentation. An alternative, of distributing raw minimum markup and formatting that to user specifications following a set number of templates ... might help. It's ironic that the article here embodies a number of PDF annoyances: - The shaded background renders quite poorly on a B&W e-ink reader (though can be eliminated with a watermark-removal setting). - The filename provides no clues as to contents or provenance, and is likely to collide with other content. - I'm a fan of serif fonts, not sans serif, for high-DPI reading. - Internal and external hyperlink support is ... variable. At times utterly missing, at others, inconsistent or inconvenient. - PDFs are not trivially directly editable, which means both authors and readers can change errors or address issues. - Many PDFs lack internal structure, even where the document they encompass do. The number of books lacking PDF table-of-contents support is ... large. - Metadata standards and practices are abysmal. See the Dublin Core standards. - Naming conventions similarly. "Report", "Resume", "Project", or "0.pdf" are names which should never be used. Describe author, content, and date, as a minimum, if possible.
In Deurbanising the Web [pdf]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.