View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013166 | MMA | General | public | 2016-03-04 15:02 | 2016-04-01 13:42 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.2.0 | ||||
| Target Version | 1.2.0 | Fixed in Version | 1.2.0 | ||
| Summary | 0013166: Switch to Google Play beta/alpha testing framework | ||||
| Description | MMA 1.2 it would probably make sense to (over the course of the release?) get rid of mediamonkeybeta and begin just using the beta/alpha testing functionality that's built into Google Play: https://support.google.com/googleplay/android-developer/answer/3131213?hl=en This could help: - prevent publishing errors before they affect the release versions of the build (especially useful in relation to multiple APK support) - expand the number of beta testers - prevent differences between test results in beta/release builds - limit negative reviews due to the fact that a version is in beta As far as what functionality to include in the new combined build (combined in the sense that a single build is used for beta testing and release); MediaMonkey (free) currently has the following limits (so that it encourages upgrades but can be used indefinitely without the upgrades): Wi-Fi Sync - limited to 7 days UPnP/DLNA - limited to 30 minutes at a time Folder browsing Configurable home screen Lyrics lookup MediaMonkey beta (free) currently expires 15 days after the last install (but has no limitations as far as any features). Moreover, updates to more recent betas reset the expiration timer so that it can be tested further without purchasing MMA Pro. I would suggest that the 'combined' build should make the following changes to the MediaMonkey (free) build so that testers can try out more (but not all) of the functionality, but have incentive to upgrade: - Wi-Fi Sync - limited to X days after install - Streaming Playback or Rendering - limited to 30 minutes at a time (for UPnP / Chromecast) - Folder browsing - limited to X days after install - Configurable home screen - completely restricted - Lyrics lookup - limited to X days after install (is this too tricky to implement?) I would suggest that X should be 15 days, and that each time a new version of the app is installed, the expiration timer is reset. (i.e. beta testers would have to purchase the app to overcome these reduced restrictions). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 584 | ||||
|
|
To clarify, should be playback from UpnpServer still limited to 30 minutes at a time or just casting to Upnp Renderer/Chromecast? |
|
|
1. There are issues in AmazonTrialTimeUtils - so the amazon build variant cannot be built. 2. Pro app doesn't unlock the MediaMonkey |
|
|
Re. UPnP playback / casting I think that all should be limited to 30 minutes at a time without the upgrade. Re. Amazon build, if you need some sort of revised spec that would allow us to create a build for Amazon, let me know. I don't consider it the highest priority though. |
|
|
To complete switch to Google Play beta/alpha testing framework we also need: A) Inform users, how to switch to new Beta: So we should publish last old Beta with dialog: The new beta version of MediaMonkey for Android is available as update of stable version. Please follow the steps below: 1)Uninstall Beta 2)Install Stable 3)Request to be tester Cancel| Uninstall [| Later] Maybe there should be also option "Later" and kept 15 days limit. During these 15 days should dialog appear every day. What do you think? I suggest that after stable version is launched, some dialog should appear like: Do you want to became a tester? No | Go for Beta And also in Options should be link to "Go for Beta" Upon click on "Go for Beta" user is redirected to "https://play.google.com/apps/testing/com.ventismedia.android.mediamonkey" User have to click on button "BECOME A TESTER", after that he should receive update for our published beta (beta has always higher version). |
|
|
I think that it shouldn't be another dialog because there are already many dialogs on startup. It can be part of eula dialog. I also think that the request link should be already in BETA dialog, so the steps should be: 1) Request to be a tester: "https://play.google.com/apps/testing/com.ventismedia.android.mediamonkey" 2) Uninstall MediaMonkey Beta 3) Install MediaMonkey |
|
|
There is provider conflict between stable and beta, so currently can't be stable and beta installed at same time. Anyway we can fix it to next builds and then steps to switch new beta can be much user-frendly. 1) Request to be a tester from Old beta via https://play.google.com/apps/testing/com.ventismedia.android.mediamonkey 2) Install new Stable (link to play store is on web side from step 1) 3) After Stable version is installed, both apps (Stable/Old Beta) are able to detect it and inform. We already have dialog for this with message: Another instance of MediaMonkey application was detected on this device. Please uninstall the other MediaMonkey applications to ensure that only one instance of MediaMonkey is installed. Thank you. <OK> Maybe we should modify it to: Old MediaMonkey Beta application was detected on this device. Please uninstall it to ensure that only one instance of MediaMonkey is installed. Thank you. <Uninstall Beta> |
|
|
(1) Re. existing beta testers, I think it's ok for the 'MediaMonkey Beta' build to display a dialog since this is a one-time event associated with the migration from 'MediaMonkey Beta' to 'MediaMonkey'. With that in mind, I agree that build 556 (the final MediaMonkey Beta build) should display: MediaMonkey Beta The 'MediaMonkey Beta' product is being replaced with a beta version of 'MediaMonkey'. If you wish to continue beta testing MediaMonkey, please following the steps below: 1)Uninstall 'MediaMonkey Beta' 2)Install 'MediaMonkey' 3)In the 'About' dialog, click 'Register for test builds' This beta build will expire in [30] days. Cancel| Uninstall (2) Re. the message within MMA, yes, we should change it to: An instance of 'MediaMonkey Beta' was detected on this device. Please uninstall it and ensure that only one instance of MediaMonkey is installed. Thank you. <OK> (3) In the MMA About dialog, below the 'Send logs' section add an entry: Register for test builds Get updated with the latest MediaMonkey beta builds. (links to https://play.google.com/apps/testing/com.ventismedia.android.mediamonkey ) (4) Also--we'll let users in our beta forum know that: Hi, This is to let you know that that moving forward, MediaMonkey for Android beta builds will be available as 'MediaMonkey' builds via the play store (we will no longer be updating the 'MediaMonkey beta' builds. The reason for this change is because: a) it'll allow you to switch between beta and release builds without having to uninstall MediaMonkey b) it'll help us expand our beta-testing user base c) it'll help help us manage the transition from Alpha to Beta to Release more efficiently d) it'll eliminate test artifacts If you're a current beta testing (using 'MediaMonkey Beta'), here's how to make the switch: 1) Register for the new beta via: https://play.google.com/apps/testing/com.ventismedia.android.mediamonkey 2) Uninstall 'MediaMonkey Beta' and delete any MMA Device Sync profiles from MediaMonkey for Windows. This will delete existing settings, and you'll have to resync from scratch, but it's a one-time operation. 3) Install the latest version of MediaMonkey beta via https://play.google.com/store/apps/details?id=com.ventismedia.android.mediamonkey&hl=en You'll automatically be updated with the latest builds as they're released. |
|
|
(2) and (3) Fixed in build 1.2.0.0582 |
|
|
(1) Fixed in build 1.1.3.556 (2) Button updated to <Uninstall> because user has no other option. in build 1.2.0.0584 |
|
|
Verified 556/586. |
