Have a feature request?

How can Screvi be more useful to you? What features are missing?

Make sure to mention if it’s on the mobile app, web or a generic feature

Planned

Option to Exclude Specific Sources from General Highlight Review

Please add a toggle or setting that allows users to exclude specific sources from the general/global Highlight Review feed, while still keeping those highlights accessible when opening the source directly. The Problem Currently, all highlights are pooled into the general review feed. While this is great for general knowledge, it can lead to "review pollution." Sometimes, I take notes on highly specific, situational topics. When these niche highlights surface during a general review session, they disrupt the flow and aren't relevant to my daily context. Use Case & Examples Not all notes serve the same purpose in a spaced repetition or review context: Keep in General Review (Broad Lessons): If I read a book on leadership or philosophy, I want those highlights surfacing regularly to keep the core lessons fresh in my daily life. Exclude from General Review (Situational Skills): If I watch a YouTube tutorial teaching a specific software skill or technical workflow, I absolutely want to save those highlights and notes. However, I only want to see them when I specifically open that source to practice that skill. I don't want a random technical instruction popping up in my daily review feed. Proposed Solution Introduce a simple "Include in Global Review" toggle (defaulted to 'On') at the source/document level. If turned Off, the highlights remain safely stored and can be reviewed manually by opening that specific source. The general Highlight Review feed remains curated, uncluttered, and relevant to the user's broader learning goals.

delta 13 days ago

In Progress

AI-Based "Smart Import" for Highlights

While Screvi already handles imports well, importing highlights from third party ebook ecosystems like Google Play Books, Moon+ Reader, or KO Reader remains a friction point. These apps don’t have clean or consistent highlight formatting, requiring one to manually do this or pass it through an AI system prior to import. I propose adding an AI-driven "Smart Import" option. This feature would intelligently parse raw text or .doc files from these apps, separating the actual highlight from the junk data automatically. Why this is better: Format Agnostic: Users don't need to wait for specific "Google Play" or "XYZ" import tools; the AI adapts to any text structure instantly. Intelligent Cleanup: Automatically strips out citations, page numbers, and "Copied from..." boilerplates that standard regex importers miss.

delta About 2 months ago

1

Workspace Segmentation (Work vs. Personal Profiles)

I would like to suggest a "Profile Switcher" to toggle between distinct Work and Personal environments. Key Functionality Ingestion: Ability to route sources (articles/videos) as "Work" or "Personal" upon saving. Scoped Review: The "Daily Review" and Feed should only show highlights relevant to the active profile (e.g., no technical tips or highlights appearing during weekend leisure review). Separate Exports: Allow "Work" highlights to sync to one destination (e.g., Enterprise Notion) and "Personal" highlights to another (e.g., Obsidian/Private Notion). Why This Helps Prevents Context Switching: Keeps work stress out of leisure time and "fluff" out of professional workflows. Data Hygiene: Ensures professional notes don't mix with personal journals or hobbies in external tools. Encourages Diverse Usage: Users will be more willing to add dry/technical work documentation knowing it won't pollute their personal library.

delta About 1 month ago

Planned

[Enhancement] Support parsing of multi-line highlights in Markdown importer

The current Markdown importer is unable to correctly parse highlights that contain line breaks. While single-line highlights import without issue, any highlight spanning multiple lines is either ignored, broken into separate fragmented highlights, or causes the import to fail. This is a significant blocker for users working with complex data. For example, my use case involves language learning where a single "highlight" consists of three distinct lines: The target language text The phonetic pronunciation The translation Personally, I have a dataset of over 1,700 highlights. Because a large portion of these are multi-line, manual entry or manual correction is not a feasible workaround.

delta About 2 months ago

3