What's the best way to test first user experience?

For our mobile game we want QA to be able to simulate the effect of a new user installing the game, even though playfab will have seen this device before.

Our QA have tried using the delete-player button in the player page of the dashboard, but subsequent installs weren't able to register the device ID through frictionless login, returning a 409 conflict error, presumably because the old account still existed somewhere and was holding onto the ID.

What's the proper procedure for reproducing clean install, and if there are danging accounts out there how do we find and clean them?

1 Reply

Typically with a mobile device you create a playfab account with their device ID, LoginWithIOSDeviceID/LoginWithAndroidDeviceID...

Then if the user chooses too, they can associate email/facebook/etc with their account.

If you want the user to be able to start from scratch, or if you want QA to be able to start from scratch, you can then unlink the account.

UnlinkIOSDeviceID/UnlinkAndroidDeviceID

And when you call this and it completes successfully, at that point reset any in-game settings you have, IE playerprefs, and locally stored data, and then set the app back to the beginning, at that point calling LoginWithIOSDeiveID/LoginWithAndroidDeviceID will setup a new account (assuming you have the createAccount boolean set to true, it is by default) and your user can start anew, or your QA can simulate a new user.

You're talking about the APIs, right? For a QA who only has access to the dashboard, is it equivalent for them to do the following:- QA finds their old account in the dashboard- QA deletes the device ID from the bottom of the player screen- QA _doesn't_ delete the player entirely, because it's not necessary??- QA reinstalls the game on their device and launches it, automatically creating a new device-linked account