NEOINK
An everyday object became a place to experiment with reading, learning, and interface design.
Where it began
I spend a lot of time reading on an e-ink device. Using the same small screen every day made me interested in the details of its software: how a library is organized, how a document reads, and what else the device could do.
NEOINK grew from that interest. It is a fork of CrossInk for the Xteink X3/X4, rather than a claim to have written the entire operating system from scratch.
My additions
My work extends the reading experience with flashcards, native Markdown reading, a richer SD-card library, INX themes, and a redesigned web interface.
I also worked on the GitHub Actions pipeline and the SD-card font pipeline. These less visible pieces matter because they make changes easier to package and maintain.
Working with an existing foundation
Open-source work involves understanding the system already there, respecting its authorship, and making the boundary of a contribution clear. CrossInk is the foundation; NEOINK is my extension of it.
The repository is the place to inspect the implementation and follow its development.
What this project means to me
This is one of the clearest connections between my interests. Reading led to software work, and software became a way to make the reading device fit how I use it.
The result is personal, practical, and unfinished in a useful way: I keep encountering things I would like to improve.
Follow the work.
NEOINK source and development historyPersonal contributions are described by Foysal. Organization-wide results remain attributed to the relevant team or public record.