Review Apps for Mobile Future Iterations

Looking at the setup instructions for Review Apps for Mobile, there are a few ways to improve the overall experience. This issue aims to capture various approaches to follow up on in future iterations.

Artifact Detection

The most complicated and error-prone part of the setup process is configuring and setting the artifact path. It's easy to misconfigure the path reference, which would cause the emulator deployment to fail. If we were able to inspect a project's configuration and pipelines, we could provide a process where a user can select the artifact they want to use, and we can generate the correct path information for them. This would eliminate several potential failure points.

Suggested CI Configuration

Building on top of Artifact Detection, we could extend it to provide a full suggested CI configuration given the artifact supplied by the user. In this scenario, we could provide a diff or a fully combined .gitlab-ci.yml file that could be applied to a project to enable Review App for mobile.

Embedded Appetize Integration

This type of integration would only work for paid plans due to the overhead cost, but it is possible to embed Appetize in an application. This sort of integration would eliminate some steps during the setup, and provide a more seamless experience.

Project Detection

Some form of project detection on the backend would enable us to serve more contextually relevant options given the type of project provided. In the example screenshot below, I've replaced the option to Add Kubernetes cluster (not relevant for mobile apps) with a Setup Mobile DevOps button. Some investigation into project detection for mobile has been done, but more research is necessary to define a feasible integration.