Salesforce

The Setup That Forces You to Uninstall

Opening the app for the first time feels like a promise. The login screen is clean. You enter your credentials. The app loads. Then the problems start. Records get stuck on "loading" indefinitely. The only fix is to clear the app data and reauthenticate. That means setting up the entire app again. This is not a one-time issue. It happens repeatedly. The app does not recover from a corrupted session. It just freezes. The user has to go to Settings, find the app, clear storage, and log in again. That is not a workflow. That is a punishment.

The Reports and Dashboards tabs disappear if the admin enables "Require periodic step-up authentication." The security feature is supposed to protect sensitive data. Instead, it removes access to the data entirely. The tabs do not show up in the mobile app. The user cannot view reports or dashboards on their phone. The only workaround is to disable the security setting. That defeats the purpose of having security in the first place. The app forces a choice between security and functionality. The user cannot have both. This is not a design flaw. It is a design decision. It is a bad one.

The Feature That Sends You to the Wrong Screen

Clicking a case link from an email or notification should open the case. That is the expectation. The app does not do that. It opens the Chatter feed instead. The user is left staring at a social feed when they need to work on a case. They navigate back. They try again. The same thing happens. The app does not learn. It does not adapt. It just keeps sending the user to the wrong place. The only way to reach the case is to manually search for it. That adds extra steps to a process that should be instant. The user wastes time. The app wastes their time. The app does not care.

The Chatter feed itself is a mess. Field tracking, record updates, and notifications all get lost in the noise. Important updates are buried under less important ones. The user has to scroll through dozens of posts to find the one they need. The search feature does not help. It is slow and imprecise. The app feels old. It feels like a relic from a decade ago. The Lightning experience is supposed to be modern. It is not. It is just a fresh coat of paint on a crumbling foundation.

The Performance That Gets Worse with Every Update

The app is 181.3 MB. That is massive for a mobile app. It takes up storage that could be used for photos, videos, or other apps. The size does not translate to performance. The app is slow. It lags. It crashes. The changelog says "bug fixes and performance improvements" with every update. The performance does not improve. It gets worse. The app is slower on version 262.010.0 than it was on version 250.020.0. The user notices. They complain. The developer ignores them. The cycle continues.

The iOS version is even larger at 367.3 MB. It requires iOS 17.0 or later. That locks out users with older devices. The Android version requires Android 12.0 or later. Users on Android 11 cannot install the app. They are forced to upgrade their devices or use the web version. The web version is also sluggish. The problem is not the device. The problem is the app. It is bloated. It is inefficient. It is a resource hog that delivers poor performance. The user pays for the privilege of using a slow app. That is not a good deal.

The Security Feature That Kills Productivity

The "Require periodic step-up authentication" setting is designed to protect sensitive data. It forces the user to re-authenticate periodically. That is a good security practice. The problem is that enabling this feature removes the Reports and Dashboards tabs from the mobile app. The user cannot access these critical features on their phone. The admin has to disable the setting to restore access. That is not a solution. That is a workaround. The workaround creates a security gap. The admin has to choose between security and functionality. They choose functionality. The security feature becomes useless. The app has created a self-defeating security mechanism. It protects nothing because it forces admins to turn it off.