Key Features
Tech Stack
The biggest challenge was balancing feature completeness with device limitations. Running TTS and AI fully on-device meant carefully managing memory spikes, chunking long texts, avoiding UI stalls, and working within the restrictions of Apple Intelligence availability. Getting TTS to feel continuous required experimentation with segmentation, buffering, and timing, especially for long-form documents.
Another interesting challenge was unifying such different file formats into a consistent reading experience. Rather than building multiple rendering paths, I ended up normalizing most formats into HTML and relying on CFI anchors and a WebView-based system. This reduced code surface but introduced its own edge cases, especially around selection accuracy and highlight persistence.
PDF brought its own set of problems — mainly keeping performance stable on large files and making sure overlays (search, highlights, TTS, translation) stayed synchronized with page geometry. I’m still improving this area.
I’m very interested in learning how others approach on-device inference, streaming models, memory usage patterns, and PDF performance. If anyone has experience or ideas in those areas, I’d love to hear them.
Happy to answer questions about any part of the implementation.
Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.