3 more "Nice to have" ideas...

Corona Marketplace OneSignal
#1

This is the best push platform. Thank you so very much for making it so. Your responsiveness is unprecedented. 

I have three small suggestions : 

Segments created to be sorted alphabetically on segment name on the Segments tab. 

Ability to click on a User record and delete user on the Users tab. This should then result in user record being recreated next time same user opens your app on the same device. 

Finally, striving for consistent naming should help as a sign of maturity. Ie User(s) vs Player(s). Both terms mean the same thing but are used interchangeably. I personally prefer User(s) as I feel the push service is inevitably going to be used by non-game apps as well. Better be more generic to cover all app users but thats just me. Suggest picking one or the other and making your references consistent. 

Thank you very much once again for this amazing service. Have a great weekend. 

#2

Thanks for the kinds words and suggestions Ksan!

Here are my comments for each:

Segments created to be sorted alphabetically on segment name on the Segments tab. 

Alphabetically sorting segments - Good one, & easy. We’ll have this in on our next update.

Ability to click on a User record and delete user on the Users tab. This should then result in user record being recreated next time same user opens your app on the same device. 

 

Right now if anything changes about a user (such as language, device token, and so on), we update the changes in our system. What use case do you have in mind where it would be useful to remove a user and have them re-added?

 

Finally, striving for consistent naming should help as a sign of maturity. Ie User(s) vs Player(s). Both terms mean the same thing but are used interchangeably. I personally prefer User(s) as I feel the push service is inevitably going to be used by non-game apps as well. Better be more generic to cover all app users but thats just me. Suggest picking one or the other and making your references consistent. 

Definitely. We’ve been moving towards using “User” everywhere instead of “Player” for this very reason. But there are still a couple places where we haven’t updated the text. We’ll get to changing those soon!

#3

Hi George, Thanks much once again for your response. I appreciate your support for #1 & #3 suggestions.

As for #2, the use case is mostly testing & validation. During initial app testing where I have a handful of devices I like to try things with them and sometimes the initial registration action can only be observed once per device. Obviously once we have many devices running the production version of our app this ability would be be used often if at all but during testing and development it might come in handy. Thanks for considering. 

Regards,

Kerem

#4

Thanks for the kinds words and suggestions Ksan!

Here are my comments for each:

Segments created to be sorted alphabetically on segment name on the Segments tab. 

Alphabetically sorting segments - Good one, & easy. We’ll have this in on our next update.

Ability to click on a User record and delete user on the Users tab. This should then result in user record being recreated next time same user opens your app on the same device. 

 

Right now if anything changes about a user (such as language, device token, and so on), we update the changes in our system. What use case do you have in mind where it would be useful to remove a user and have them re-added?

 

Finally, striving for consistent naming should help as a sign of maturity. Ie User(s) vs Player(s). Both terms mean the same thing but are used interchangeably. I personally prefer User(s) as I feel the push service is inevitably going to be used by non-game apps as well. Better be more generic to cover all app users but thats just me. Suggest picking one or the other and making your references consistent. 

Definitely. We’ve been moving towards using “User” everywhere instead of “Player” for this very reason. But there are still a couple places where we haven’t updated the text. We’ll get to changing those soon!

#5

Hi George, Thanks much once again for your response. I appreciate your support for #1 & #3 suggestions.

As for #2, the use case is mostly testing & validation. During initial app testing where I have a handful of devices I like to try things with them and sometimes the initial registration action can only be observed once per device. Obviously once we have many devices running the production version of our app this ability would be be used often if at all but during testing and development it might come in handy. Thanks for considering. 

Regards,

Kerem