Android Mobile SDK to easily integrate communication features (WebRTC, messaging, presence, voice, video, screensharing) based on RestComm into native Mobile Applications
The problem right now is that the id is the same and as a result developers after release just overwrite the released apk with the debug one currently developing. This means that devs don't really stay long enough actually using the production .apk and lose touch with it. Another downside until we fix contacts in the server side is that we lose the numbers too.
To address this let's consider using a debug/dev applicationId and in CI we just set applicationId to the production one. That way production .apk is left side by side with development.
Another thing we can do is add a debug watermark so that we can differentiate from icon
atsakiridis
commented
6 years ago
The problem right now is that the id is the same and as a result developers after release just overwrite the released apk with the debug one currently developing. This means that devs don't really stay long enough actually using the production .apk and lose touch with it. Another downside until we fix contacts in the server side is that we lose the numbers too.
To address this let's consider using a debug/dev applicationId and in CI we just set applicationId to the production one. That way production .apk is left side by side with development.
Another thing we can do is add a debug watermark so that we can differentiate from icon