WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

475

“App not installed” does not help anyone and solves zero issues.

Android should show the exact reason for the failure of an APK installation, in order to facilitate troubleshooting.

*“App not installed”* does not help anyone and solves zero issues. Android should show **the exact reason** for the failure of an APK installation, in order to facilitate troubleshooting.

(post is archived)

[–] 1 pt

I remember the first time my great grandmother used a computer mouse. She held it in midair and tried to move the cursor across the screen. Was she crazy or just ahead of her time and working on virtual reality controllers before anyone? I disagree and feel there should always be a layer between the casual and serious user. Apple does extremely well selling 5 year old hardware in a small form b/c it's software is nearly retard proof. Their music and graphic design software is oddly magnificent for the casual user. Yet a Mac OS doesn't even have software that let's an end user edit it's registry. That's a thing you get elsewhere.

I agree you should be able to find the reason easily enough. At what point is a feature just one bit of information too much that drives average users away?

[–] 0 pt

That's what submenus are for.

[–] 0 pt

*That's what the command line is for.

[–] 1 pt

That too, but submenus are also non-intrusive to minimalist users, and everyone would agree that showing a reason for why an installation has failed is certainlly more useful than just showing “Installation failed”.

Submenus are quicklier accessible to power users than command line, while non-intrusive to rookie users.

Both options should exist.