Lifestyle app with supported-device requirements
Split appears to be a lifestyle app that expects access through a supported installation channel. The visible launch path redirected to a requirement page asking the user to get the app from Play before continuing.
That behavior matters because users may not reach the main service on every device or installation path. Anyone installing it should confirm that the app opens normally on their own phone before depending on account, notification, or location features.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
Location, alerts, and service access
The package declares location, notifications, storage, network access, advertising identifiers, license checks, wake-lock, vibration, and push messaging capabilities. These can support nearby or account-linked behavior, alerts, and service validation.
Location and notification permissions should be enabled only when the app explains the benefit clearly. If the app continues to redirect away from the local installation, users should treat that as a compatibility limitation.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
Practical first-run review
Because the normal product interface was not reached in this run, users should verify login, profile, privacy, and any paid or location-based feature directly on their device. The Android settings pages still show useful information about permissions and storage use.
A careful first-run check helps avoid surprises such as unnecessary alerts, location sharing, or an app that cannot continue without a supported store flow. Users who need immediate access should test the launch path before removing other options.
