[Feature Request] Native Shevery API support

Open
  • Is something wrong?
#1,437 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The payload names no source files, so start by locating where Shizuku is integrated in the Android app. Before writing code, settle what the Shevery API (com.hamondev.shevery) exposes and whether the maintainer will accept the change, since the proposed solution is empty. Done would mean an agreed design plus a working integration that the maintainer can test.

Written by the indexing model from the issue text.

Description

enhancement
Guidelines
  • I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
  • I'm not requesting app support for a specific repo — that's up to repo maintainers
  • I understand this might not get built (Droid-ify is maintained by a single person)
Problem

Hello! Could you please add native support for the Shevery API (com.hamondev.shevery) alongside Shizuku? Shevery is now using its own native provider, and adding native support would allow the app to work seamlessly without needing compatibility stubs. Thanks!

Proposed solution

.

Extras

.

Dominant language
Kotlin
Stars
7.7k
Forks
232
No merged PRs in 30d

Getting set up

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.

More from Droid-ify/client

All issues in Droid-ify/client

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.