On Tue, Jan 6, 2015 at 6:57 AM, Matthias Wessendorf <email@example.com> wrote:On Mon, Jan 5, 2015 at 5:53 PM, Andres Galante <firstname.lastname@example.org> wrote:Hey!
I am working on the push console, and I have some questions:
1- What is the main action on the console? What is the main goal a user want to achieve?
I notice that the console is center on creating and seeing up apps and not so much in sending notifications. Is sending notifications usually done on code and not the console?the console is nice to send test messages. But in reality a backend (e.g. a MBaaS) will send a request to UPS to force it to deliver the push to Apple and GCM.The main goal is managaement (and overview/stats) around Apps, their Variants and their installations.
2- Under each app we have some information mixed with actions:
No variants - Activity - Send Push - admin
What does "admin" do, can an app be manage by other thats not the admin?we allow to roles:* admin* usera user (like Andres or Matthias) can do all the CRUD actions. Andres see his apps, Matthias see his own apps too. An Admin (e.g. Jay) sees apps from both users Andres and Matthias
3- Once you click on an app name you get a yellow box with "Sending push notifications" set up information. But when you create a variant you also get an specific info box for each variant.
What is the difference between them?not sure what you are asking
The first box (Sending push notifications) when you create a new application is a snippet of code to you use in you backend (using our sender API) to send a message to UPS and it delivery to the devices like it. The second box (Registering installations) when you create a variant is a snippet of code to you use in you mobile app to register you device in that application like it
aerogear-dev mailing list