Horizontal-org / Horizontal-org/Tella-Android

Feature Proposal: PDF enhancements, Secure Wipe, Quick Delete, In-App Browser

Open
#505 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
113
Forks
29
Avg merge
2d 1h
Merged PRs (30d)
9

Description

Subject: Feature Proposal: PDF enhancements, Secure Wipe, Quick Delete, In-App Browser

Hi Tella Team,

I love the app and would like to contribute code for four specific features. Before I start, I want to check if these align with your roadmap and ask a few questions.

Proposed Features:

  1. Enhanced PDF Reader: Add state persistence (remember last read page), Go to page input, Text-to-Speech (TTS) read-aloud, text highlighting, and sticky notes.
  2. Secure Wipe on Import: Prompt the user to Secure Wipe (overwrite data so it is forensically unrecoverable) the original file after importing, instead of just standard deletion.
  3. Quick Delete Security: Add a dedicated secret PIN to trigger Quick Delete, plus a configurable setting to auto-trigger it if the wrong password is entered X times in Y minutes (brute-force protection).
  4. In-App Browser: Add a built-in browser so users can browse and download directly into the app, preventing external browser traces (cache and history) from leaking outside Tella's secure environment.

My Questions:

  1. Philosophy: Do any of these features conflict with Tella's core idea or security model?
  2. Code Structure: Do you prefer new features kept in separate, modular files, or integrated directly into existing files?
  3. Merge Criteria: If I ensure the code is perfectly optimized, cleanly organized, maintainable, and clean, will you accept and merge the Merge Request?

Let me know if I should open individual GitLab issues for these first. Thanks for your great work!

Best regards,

Kazi Ar Rafi
Website: krafi.org
GitLab: gitlab.com/krafi

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the four proposals in the issue body and the project's security model; no source files, tests, or entry points are identified. Clarify roadmap fit and security requirements with the maintainers, then split the proposals into separate issues with defined acceptance criteria before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.