39 lines
1.6 KiB
Markdown
39 lines
1.6 KiB
Markdown
# Deployment Section Note
|
|
|
|
The process of uploading the Android app bundle to Google Play Console and setting up an internal test track should generally **not** be described in the `Solution` section.
|
|
|
|
## Why it does not fit `Solution`
|
|
|
|
The `Solution` section should primarily explain:
|
|
|
|
- what the product is,
|
|
- which main components it consists of,
|
|
- how those components solve the user problem.
|
|
|
|
Google Play Console setup, app-bundle upload, signing, and internal testing are not really part of the product solution itself. They are part of the **delivery and distribution process**.
|
|
|
|
## Better placement
|
|
|
|
This material fits better in one of these sections:
|
|
|
|
- `Implementation`
|
|
- if the point is to describe the practical technical work required to prepare the app for Android delivery and real-device testing
|
|
- `Discussion`
|
|
- if the point is to reflect on deployment challenges, release-readiness, signing issues, package identity, or lessons learned
|
|
- `Appendix`
|
|
- if the point is simply to document that internal testing was configured and completed
|
|
|
|
## Recommended approach
|
|
|
|
If deployment readiness is important for the report, the cleanest solution is:
|
|
|
|
- keep `Solution` focused on the app as a product,
|
|
- mention Android deployment and internal testing in `Implementation`,
|
|
- mention any notable release problems or limitations in `Discussion` if relevant.
|
|
|
|
## Short report-friendly summary
|
|
|
|
If needed, a short version could be phrased like this:
|
|
|
|
> Preparation for Android deployment, including app-bundle generation and Google Play internal testing, was treated as part of the implementation and delivery process rather than as part of the product solution itself.
|