Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why not have Mastodon and Lemmy Redirect be in the same app? #18

Closed
Jaoheah opened this issue Aug 22, 2023 · 1 comment
Closed

Why not have Mastodon and Lemmy Redirect be in the same app? #18

Jaoheah opened this issue Aug 22, 2023 · 1 comment

Comments

@Jaoheah
Copy link

Jaoheah commented Aug 22, 2023

i was just wondering why they are seperate apps. Maybe you could just have them be in the same app, and you could rename it to Fediverse Redirect?

@zacharee
Copy link
Owner

I have a few reasons for that:

  1. Mastodon Redirect alone is handling over 18,000 domains. Depending on what version and skin of Android you're running, that's enough to make Settings crash when you try to open App Info. I'm working on reducing the number while keeping most functionality, but it's always going to be a lot. Adding Lemmy Redirect's 3,000+ domains (and growing) to the mix is just going to make that problem worse. (Also, Android Studio gets pretty slow when editing the massive manifest files.)
  2. I can't really think of a good way to put the selector for both into one app. UI considerations aside, Android doesn't have a great way to list your own app's deep links and categorize them (Mastodon vs. Lemmy), especially below Android 12, so I would probably have to implement my own parsing for every handled link to know where to send it.
  3. Some people might use Mastodon and not Lemmy or vice-versa. Separate apps means people can choose which service they want to have handled without needing extra granular controls for deselecting/selecting domains by category (see above for why that's hard to do).

I know 15MB per app isn't exactly tiny (Jetpack Compose is responsible for most of that), but since they don't store any data aside from a few preferences, they shouldn't ever take up more than the 15MB for the app and whatever extra Android generates when optimizing installed apps.

@zacharee zacharee mentioned this issue Jan 13, 2024
@zacharee zacharee pinned this issue Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants