MyEsse

The onboarding flow and what happens after the first tap

The installation completes. The app icon appears on the home screen. Tapping it opens a login screen. No guest mode exists. The app requires Esselunga employee credentials. This is the first barrier to entry. The login screen has two fields: username and password. Below them, a "Forgot Password?" link. The link opens a web view. The web view points to the Esselunga corporate portal. The app does not handle password recovery natively. It redirects to the company's IT systems. This is a deliberate design choice. It keeps authentication centralized. The login process feels like a corporate intranet. There is no biometric login option. No fingerprint or face recognition. The user must type credentials every time. This is a limitation for frequent users. A store employee checking schedules multiple times a day must re-enter credentials. The app does not remember the session for long. The session timeout is likely set by corporate policy.

After successful login, the home screen loads. The home screen displays a news feed. The feed shows company announcements. The announcements are sorted by date. The newest appears at the top. Each announcement has a title, a short description, and a timestamp. Tapping an announcement opens the full text. The full text view includes images and links. The links open within the app's web view. The web view does not support external browsers. This keeps the user inside the app ecosystem. The home screen also has a bottom navigation bar. The bar has four tabs: Home, Documents, Communities, and More. The Home tab is the default. The Documents tab lists personal files. The files include payslips, contracts, and HR forms. The files are stored in the company's document management system. The app retrieves them via API calls. The retrieval speed depends on the network connection. A slow connection results in a loading spinner. The spinner can persist for several seconds. This is a common frustration point.

How company news and themed communities interact in practice

The Communities tab is the second major feature. It lists themed groups. The groups are based on interests or departments. Examples include "Sustainability," "Innovation," and "Store Operations." Each group has a description and a member count. Tapping a group opens its feed. The feed shows posts from members. The posts can be text, images, or links. Members can like and comment on posts. This creates a social layer within the app. The social layer is separate from the news feed. The news feed is for official communications. The communities are for peer-to-peer interaction. This distinction is important. Official news cannot be commented on. Communities are for discussion. The two features operate in parallel. They do not intersect. A news announcement about a new sustainability initiative does not automatically appear in the Sustainability community. A community member must manually share it. This creates a gap. The app does not bridge official news and community discussion. The user must navigate between tabs to see both. This is a missed opportunity for integration.

The app also includes an "Initiatives" section. This is under the More tab. The Initiatives section lists company events. The events include training sessions, volunteer opportunities, and social gatherings. Each event has a date, time, location, and description. Users can register for events directly in the app. The registration process is simple. It requires a single tap. The app sends a confirmation notification. The notification appears in the system tray. The app does not have an in-app notification center. All notifications are push notifications. This is a limitation. A user who misses a push notification has no way to see past alerts. The notification history is not stored. The app relies entirely on the device's notification log. This is a common design flaw in internal communication apps.

Comparing the document access feature to a standard HR portal

The document access feature is similar to a standard HR portal. However, the mobile implementation has limitations. The desktop version of the Esselunga portal allows bulk downloads. The mobile app does not. Each document must be downloaded individually. This is inefficient for users who need multiple payslips. The app also does not support offline access. Documents are not cached. Each view requires a fresh network request. This is a problem in areas with poor connectivity. Store basements often have weak signals. An employee in a basement cannot access their payslip. The desktop version does not have this limitation. It works over any internet connection. The mobile app's reliance on real-time data is a weakness.

The app also lacks a search function for documents. Users must scroll through a list to find a specific file. The list is sorted by date. The newest appears first. This is helpful for recent documents. It is not helpful for older documents. An employee looking for a contract from two years ago must scroll extensively. The app does not have filters or categories. All documents are in one list. This is a significant usability issue. The desktop portal has a search bar and filters. The mobile app is a stripped-down version. This is a common pattern for mobile HR apps. The focus is on convenience, not feature parity. The app is designed for quick checks, not deep dives.

The version history and the missing changelog

The Play Store listing does not show a version changelog. The "What's New" section is absent. This is a notable omission. Most apps include some update notes. The absence suggests the developer does not prioritize transparency. The app's version history is not publicly available. Users cannot see what changed in the latest update. This is a concern for IT departments. They need to know about security patches. The lack of a changelog makes it difficult to assess risk. The app may have received critical security updates. There is no way to know. The developer, Esselunga SPA, is a large company. They have the resources to provide a changelog. The omission is likely a deliberate choice. The app is internal. The company may assume employees do not need to know about changes. This assumption is flawed. Employees deserve to know what is being installed on their devices.

The app's rating on third-party trackers is 2.5 stars. This is a low rating. It suggests user dissatisfaction. The low rating may be due to performance issues. The app may crash or lag. The Play Store page does not show user reviews. The reviews are hidden or not displayed. This is unusual. Most apps show reviews. The lack of visible reviews is a red flag. It may indicate the developer has disabled reviews. This is possible for internal apps. The app is not meant for public consumption. The target audience is Esselunga employees. The company controls the distribution. The app is not marketed to the general public. This explains the lack of public reviews. The app is a tool, not a consumer product.

Technical detail: the app's reliance on the corporate network and single sign-on

The app uses the company's single sign-on (SSO) system. The login credentials are validated against Esselunga's Active Directory. The app does not store credentials locally. All authentication is handled server-side. This is a security best practice. The app does not have a "Remember Me" option. This is also a security measure. It prevents unauthorized access if a device is lost. The session token is stored in the app's secure storage. The token expires after a set period. The expiration time is not configurable by the user. The app automatically logs out after the token expires. The user must re-enter credentials. This is a minor inconvenience for a significant security gain. The app also requires an internet connection for all operations. There is no offline mode. Every action requires a network request. This includes viewing documents. The document is downloaded each time it is opened. The app does not cache documents locally. This is a data usage concern. Employees on limited data plans may incur charges. The app does not have a setting to limit data usage. This is an oversight.