Systems and methods for providing mobile proving ground
The disclosed embodiments include methods, systems, and articles of manufacture for enabling beta testing of new features within a native application. In one embodiment, a native application executed by a client device may include executable instructions that are activated and executed only upon indication of a user belonging to a beta test group. The client device may receive a signal from a service or content provider that includes test group information indicating whether a user is a member of a test group. The client device may process the received signal to determine whether the user is a member of a test group and, if so, activates and executes certain instructions received as part of the native application that define a user interface enabling access to additional functionality unavailable to a user determined not to be a member of a test group.
1. A system for determining beta feature sets for a plurality of users based on test groups, the system comprising:
storage circuitry configured to store a native application, at a client device, comprising a non-beta feature set and a beta feature set, the beta feature set comprising new beta features or updated beta versions of non-beta features of the beta feature set; and
control circuitry configured to:
receive a first user request, from a first user of the plurality of users, to access the native application;
in response to receiving the first user request, determining whether to enroll the first user in a first test group or a second test group, wherein the first test group is associated with testing first beta features of the beta feature set, and wherein the second test group is associated with testing second beta features of the beta feature set that are different from the first beta features;
in response to enrolling the first user in the first test group;
enable the first user to access the first beta features and the non-beta feature set via a first instance of the native application executing on the client device;
generate for display, in a first instance of the native application on the client device, a first set of icons, wherein the first set of icons are related to the first beta features and the non-beta feature set; and
in response to enrolling the first user in the second test group:
enable the first user to access the second beta features and the non-beta feature set via the first instance of the native application executing on the client device;
generate for display, in the first instance of the native application on the client device, a second set of icons, wherein the second set of icons are related to the second beta features and the non-beta feature set.
2. A non-transitory computer-readable medium storing instructions executable by at least one processor to perform operations for determining beta feature sets for a plurality of users based on test groups, the operations comprising:
receiving a first user request, from a first user of the plurality of users, to access a native application, at a client device, wherein the native application comprises a non-beta feature set and a beta feature set, wherein the beta feature set comprises new beta features or updated beta versions of non-beta features of the beta feature set;
in response to receiving the first user request, determining whether to enroll the first user in a first test group or a second test group, wherein the first test group is associated with testing first beta features of the beta feature set, and wherein the second test group is associated with testing second beta features of the beta feature set that are different from the first beta features;
in response to enrolling the first user in the first test group, enabling the first user to access the first beta features and the non-beta feature set via a first instance of the native application executing on the client device; and
generating for display, in a first instance of the native application on the client device, a first set of icons, wherein the first set of icons are related to the first beta features and the non-beta feature set.
3. The non-transitory computer-readable medium of claim 2 , the operations further comprising:
in response to enrolling the first user in the second test group, enabling the first user to access the second beta features and the non-beta feature set via the first instance of the native application executing on the client device; and
generating for display, in a first instance of the native application on the client device, a second set of icons, wherein the second set of icons are related to the second beta features and the non-beta feature set.
4. The non-transitory computer-readable medium of claim 2 , the operations further comprising:
storing test group identification information for the plurality of users; and
accessing the test group identification information to determine whether to enroll the first user in the first test group or the second test group.
5. The non-transitory computer-readable medium of claim 4 , further comprising:
determining a subgroup of the first user based on the test group identification information for the plurality of users; and
selecting the first user in the first test group based on the subgroup.
6. The non-transitory computer-readable medium of claim 2 , further comprising:
monitoring a length of time that the first user accesses the first set of icons; and
transmitting the length of time to a remote device.
7. The non-transitory computer-readable medium of claim 2 , further comprising:
monitoring a frequency of interactions of the first user with the first set of icons; and
transmitting the frequency of interactions to a remote device.
8. The non-transitory computer-readable medium of claim 2 , further comprising:
monitoring a number of requests from the first user for additional assistance; and
transmitting the number of requests to a remote device.
9. The non-transitory computer-readable medium of claim 2 , further comprising:
monitoring a time when the first user exits the native application; and
transmitting the time to a remote device.
10. The non-transitory computer-readable medium of claim 2 , further comprising:
receiving an initial request from the first client device to download the native application to the first client device; and
in response to the initial request, accessing the test group identification information to determine whether to enroll the first user in the first test group or the second test group.
11. The non-transitory computer-readable medium of claim 2 , further comprising:
selecting a current feature in the first beta features; and
dynamically updating the current feature.
12. A method for determining beta feature sets for a plurality of users based on test groups, the method comprising:
receiving a first user request, from a first user of the plurality of users, to access a native application, at a client device, wherein the native application comprises a non-beta feature set and a beta feature set, wherein the beta feature set comprises new beta features or updated beta versions of non-beta features of the beta feature set;
in response to receiving the first user request, determining whether to enroll the first user in a first test group or a second test group, wherein the first test group is associated with testing first beta features of the beta feature set, and wherein the second test group is associated with testing second beta features of the beta feature set that are different from the first beta features;
in response to enrolling the first user in the first test group, enabling the first user to access the first beta features and the non-beta feature set via a first instance of the native application executing on the client device; and
generating for display, in a first instance of the native application on the client device, a first set of icons, wherein the first set of icons are related to the first beta features and the non-beta feature set.
13. The method of claim 12 , further comprising:
in response to enrolling the first user in the second test group, enabling the first user to access the second beta features and the non-beta feature set via the first instance of the native application executing on the client device; and
generating for display, in a first instance of the native application on the client device, a second set of icons, wherein the second set of icons are related to the second beta features and the non-beta feature set.
14. The method of claim 12 , further comprising:
storing test group identification information for the plurality of users; and
accessing the test group identification information to determine whether to enroll the first user in the first test group or the second test group.
15. The method of claim 14 , further comprising:
determining a subgroup of the first user based on the test group identification information for the plurality of users; and
selecting the first user in the first test group based on the subgroup.
16. The method of claim 12 , further comprising:
monitoring a length of time that the first user accesses the first set of icons; and
transmitting the length of time to a remote device.
17. The method of claim 12 , further comprising:
monitoring a frequency of interactions of the first user with the first set of icons; and
transmitting the frequency of interactions to a remote device.
18. The method of claim 12 , further comprising:
monitoring a number of requests from the first user for additional assistance; and
transmitting the number of requests to a remote device.
19. The method of claim 12 , further comprising:
monitoring a time when the first user exits the native application; and
transmitting the time to a remote device.
20. The method of claim 12 , further comprising:
receiving an initial request from the first client device to download the native application to the first client device; and
in response to the initial request, accessing the test group identification information to determine whether to enroll the first user in the first test group or the second test group.