I am planning to start on Transdroid 3. It will be a full rewrite and redesign.
- The networking stack of Transdroid 2 is ancient and still uses the legacy Apache http client API (via org.apache.http.legacy).
- The UI is showing age and uses layers of patches upon old appcompat components that frequency break (such as the app bars recently).
- We rely on unsupported and unmaintained libraries such as androidannotations, ormlite and very old UI components.
- We still use deprecated XML layouts which get no love, and Java which no-one loves.
- There are many features poorly which might or might not work any more (search module content provider, broken tablet layout, several totally untested torrent client adapters).
A fresh start should:
- Use modern language, tooling, libraries (Kotlin, Compose UI, okhttp...)
- Focus again on most-used, most-loved, most-wanted features and clients
- Have proper CI/CD, releases probably on F-Droid
- Make it fun to work in the code base
I hope to do this together with the community. It will stay 100% open-source (GPL). I would love your feedback. What torrent clients should we support? Which features really need to stay (or can we do without)? Should be keep the Play Store-friendly version?
I am planning to start on Transdroid 3. It will be a full rewrite and redesign.
A fresh start should:
I hope to do this together with the community. It will stay 100% open-source (GPL). I would love your feedback. What torrent clients should we support? Which features really need to stay (or can we do without)? Should be keep the Play Store-friendly version?