Is this possible: Multiple sign-ups with the same Package Name but each with a different Role Account Email?

[Streets Of Boston]

Hi,

I think the answer to my topic's question is 'Yes', but I just am not quite sure about it.

Our company sells software that is installed as web and app servers on our customers' sites. The software is configured for each particular customer (roles, rules, profiles, etc.). When the server is all configured, it is put into production at the customers' sites and used by the customers(=employers)' employees.

The employees can download an Android app that takes a base URL to communicate with their employers server. The Android app is a REST based app.

The Android app is the same app for each employee for every employer. The only thing that differs from each employer is the base URL to the employer's server.

At some point, we'd like to implement server-push using C2DM. 

My question is:

Since there is only one Android app out there (one Package Name) for many server-installations on customers' sites (many Role Account Emails), is it possible to sign-up multiple times, each time with the same Package Name but a different Role Account Email?

Thanks!

[Jake Churchill]

I did it.  I was using one sender for development and I signed up for a new sender for production but the same package name.  I didn't have an issue.

-Jake

[Streets Of Boston]

Thanks, Jake!

If it works for 2 sender-ids, i assume it'll work for (waaay) more than 2 as well: The number of customers (i.e. sender-ids/role-email-accounts) could run in the 100s. I hope my assumption is correct :-)

[Costin Manolache]

To clarify: this is not quite the intended use, but I think it will work as long as the app on each device uses the corresponding role when registering AND each role account is signed-up for C2DM and gets quota ( if it needs more than the ~100k default).

 

An app can't register 2 different sender IDs - there is a single record for an (android-id + app id), the second registration will replace the first one and the first sender won't be able to send. 

In any case - this is not a 'supported' feature right now, but sounds reasonable.

Please don't use one sender account shared with multiple customers - besides TOS you may 

run into other problems.

Costin

[Streets Of Boston]

Say an 'employee' has our app installed on his/her device and the app links to the server of his/her 'employer' (and the employer is our customer).

Each employer will have a unique Role (Role account Email). Our team will make sure that the employer is signed-up properly with C2DM. Note that since the client app is shared amongst ALL our customers (downloaded from Android Market), there is only one Package Name.

"To clarify: this is not quite the intended use, but I think it will work as long as the app on each device uses the corresponding role when registering AND each role account is signed-up for C2DM and gets quota ( if it needs more than the ~100k default)."

The answer are 'yes' AND 'yes' :-): 

The app-installation on each employee's device uses his/her employer's Role: The app gets the Role-value after the employee uses the app to log into his employer's server successfully. After a successful log-in, the app will use this employer-unique Role to register itself.

Your point about not using a shared send account is the exact thing we'd like to avoid. If one of our customer's server or client-apps are misbehaving (violating the TOS), we don't want that to affect every other customer that we have as well.

Thank you for your help!