After about a month of endless cycle of try & scrap designs I think I'm ready present my redesign of the Magisk Manager. At this point I have covered every main screen that you (user) will come in contact with, now it's time to start implementing (or rather rewriting) code from the old app to the new one.
Don't get me wrong, I'm far away from from done; but! I have a sneak-peek of what's to (hopefully) come - considering John will ultimately accept my pull request, lol.
I'm an android (app) developer by occupation and I use Magisk almost every day. I love my work and everything I do, so I decided to help John with a redesign - so the app is less generic and additions (as far as features go) are easier to implement with less of a boilerplate. I have no idea if anybody would even care about the redesign so I would love to hear your thoughts!
At work I'm kinda more appreciated as a developer than a designer so I was never actually allowed to design any production app.
The apk is work of about 10 days and roughly 40 commits.
It's mainly written in Kotlin (yey!) with a help from databinding, which makes everything much cleaner.
On top of that I use a "framework" which is actually more of a anti-boilerplate collection of libraries (jetpack wrapper) for all Android stuff - such as activites, fragments, viewmodels and interaction between them. (Can't post links since >that's whatchu get for mainly using reddit< I guess.) Nevertheless bye bye recyclerview and viewpager adapters, bye bye littering code with animations and other UI stuff.
Few of my friends reported that the app is marked as malicious by Google Play Protect, maybe because it contains johns original package name + "debug". I know what it looks like, new user, no posts, malicious app warning. Meh. It's not, build it from source, inspect it on GitHub if you don't trust me.
Also it contains Manifest permission for connecting to the internet - this is not implemented yet and does not connect to anything. Everything you see is offline mock data or your own installed apps. Again, inspect source if you don't trust me.
It might crash on APIs<21 due to some unresolved xml setters and usage of vector resources. I'll fix that once everything else is done, don't mind that.
Some visual bugs might occur, refrain from reporting it please.
This is just a preview. DESIGN PROTOTYPE
NO DOWNLOAD. Already working on a official manager. Stay tuned.
So what now?
Well, tell me how you like it!
What really bothers you in the new redesign that could be changed for the better?
What do you really like?
And yeah! almost forgot. I was wondering if redoing preferences would be better or worse. Do you prefer standard (support library-based) or entirely custom (with the super fancy dialog ripped from Android Q that you can preview while selecting Dark Mode in settings)?