merchmix-android-app
currentAn Android application for the Merchmix Core product. The repository builds and packages a mobile app, includes Android resources and launcher shortcuts for scan, search, and Today, and contains integration points for Merchmix production APIs and a forecast service. The available evidence does not establish the full set of implemented screens or business workflows.
Business summary
This is Merchmix’s mobile app for accessing core retail-planning information on Android. It appears to support a Today view and forecast-related data, with quick actions for scanning and searching, but the available repository evidence is not sufficient to describe the complete retailer experience.
Capabilities
4Provides mobile access to forecast-related information used in the Merchmix Core experience, including the Today view.
The CI configuration explicitly references Predict/Today forecast API calls and a required forecast-service API key. The implementation details and supported forecast measures are not visible in the supplied repository evidence.
Lets retail users access Merchmix information from an Android device through mobile views and quick actions.
The repository is an Android application and includes launcher shortcuts named scan, search, and today. The underlying data workflows and screen implementations are not established by the available file listing.
Retrieves Merchmix data from backend services for use in the mobile application.
The CI configuration refers to real Merchmix production APIs and includes an API key for forecast calls. Integration-test infrastructure also references client_id, access_token, and refresh_token credentials, demonstrating authenticated backend access, but not the complete API contract.
Produces installable Android builds for development and release distribution.
Gradle Android project files, Android resources, CI build steps, release signing configuration, and release APK/AAB artifacts are present or referenced. This is a delivery capability rather than a retailer business workflow.
Workflows
2A mobile user opens the Today or forecast-related experience to retrieve current Merchmix information.
- 1.Launch the Android application or use the Today launcher shortcut.
- 2.Authenticate against the applicable Merchmix backend if required.
- 3.Request forecast/Today data from the backend services.
- 4.Display the returned information in the mobile application.
CI validates and packages the Android application, with tagged builds optionally producing signed release artifacts.
- 1.Run lint and unit tests.
- 2.Build the debug application for normal branch and pull-request pipelines.
- 3.For a v* tag, configure release signing credentials when a signed artifact is required.
- 4.Build and publish the release AAB/APK as a pipeline artifact.
Architecture
Native Android application packaged with Gradle. The app communicates with Merchmix backend APIs, including a forecast service, and includes Android resources, launcher shortcuts, Firebase configuration, and CI/CD build automation.
Interfaces
4| Kind | Identifier | Description |
|---|---|---|
| other | Android application | Installable Android application with launcher icons and shortcuts for scan, search, and Today. |
| http | Merchmix production APIs | Backend API integration used by the app; the supplied evidence does not provide route names or a formal API specification. |
| http | Forecast service API | Forecast API used by Predict/Today functionality and authenticated with a forecast API key. |
| cli | Gradle wrapper | gradlew and gradlew.bat provide the build and test command-line interface. |
Screens
3| Route | Name | Purpose |
|---|---|---|
Today launcher shortcut | Today | Quick entry point to the app’s Today experience, which is associated with forecast API calls. |
Scan launcher shortcut | Scan | Quick entry point labelled for scanning; the exact scanned object and resulting workflow are not established. |
Search launcher shortcut | Search | Quick entry point labelled for search; the searchable data and result behavior are not established. |
Data
3| Entity | Ownership | Description |
|---|---|---|
| Forecast and Today data | reads | Forecast-related information retrieved for the mobile Predict/Today experience. |
| Authenticated API session credentials | reads | Client and access/refresh tokens used by live API integration tests and, by implication, authenticated backend access. Secret values are not included. |
| Application configuration | owns | Android and Google/Firebase application configuration packaged or referenced by the app. |
Dependencies
5| Name | Kind | Relationship | Criticality |
|---|---|---|---|
| Merchmix production APIs | internal service | calls | critical |
| Forecast service | internal service | calls | critical |
| Firebase/Google services | external service | uses | supporting |
| Android SDK and Gradle | library | depends_on | critical |
| Bitbucket Pipelines | other | uses | supporting |
Technology
Limitations
6- —The supplied evidence does not include a complete source-file listing, so the actual UI, API clients, domain models, and business rules cannot be fully assessed.
- —No API route names, schemas, backend ownership boundaries, or network library are established.
- —Scan and search are evidenced only by launcher shortcut resources; their business meaning and implementation are unknown.
- —The evidence does not establish support for WSSI, OTB, Range Planning, Size Curve, Markdown, Allocation, Replenishment, Option Planning, Buying, or Assortment Planning workflows.
- —The CI configuration documents live production integration tests, but this repository should not be treated as a safe environment for executing them without the explicit opt-in and production-safety precautions described there.
- —The repository contains google-services.json and the pipeline references secret configuration, but secret values and their contents are intentionally not described.
Agent instructions
Treat this repository as the Android client for Merchmix Core, with confirmed forecast/Today API integration and build/distribution responsibilities, but do not assume broader merchandise-planning capabilities without source evidence.
- →Route Android build, packaging, launcher, or mobile UI questions here.
- →Route forecast or Today mobile-access questions here when the request concerns the Android client; distinguish this from ownership of forecast calculations, which is not established.
- →Do not claim that the app implements specific planning domains such as OTB, allocation, or replenishment based only on the product name.
- →Do not run live API integration tests against production unless the explicit instrumentation opt-in is intentionally provided and the caller has confirmed the production-risk controls.
- →Do not request, expose, or infer values for API keys, tokens, keystores, or signing passwords.