<div dir="ltr">?! I can do it worse: uninstall the app because it drains the battery.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 1, 2014 at 2:14 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 03/31/2014 02:03 PM, Miiguel Lemos wrote:<br>
> Using the GCM for push notifications has a very important advantage: it minimizes the battery consumption, since it reduces the processor overload, it's not needed to open a socket to check the server on a regular basis, etc. In my opinion this a critical matter, minimizing the probability of the user turning the notifications off.<br>
</div>On Android you can't turn notifications off in the same way as iOS.<br>
<div class="HOEnZb"><div class="h5">><br>
><br>
> Enviado do meu iPad<br>
><br>
> No dia 31/03/2014, às 18:51, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>> escreveu:<br>
><br>
>> I would vote for A<br>
>><br>
>> --<br>
>> abstractj<br>
>><br>
>> On March 31, 2014 at 10:59:01 AM, Summers Pittman (<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>) wrote:<br>
>>>> Y'all,<br>
>>> So there has been some concerns with the complexity of the build<br>
>>> especially where including the Google GCM (push) libraries<br>
>>> are<br>
>>> concerned. Additionally there have been some requests for a<br>
>>> separate<br>
>>> "push" module which won't need the full aerogear android library.<br>
>>><br>
>>> The full modularization of the library along with several other<br>
>>> improvements is scheduled for the "2.0" epic.<br>
>>><br>
>>> So my question is a) Should we make a 2.0 which is only the<br>
>>> modularization sooner and iterate on that a few times before<br>
>>> we include<br>
>>> our improvements in a 3.0 or b) Should we create a "fork" project<br>
>>> which<br>
>>> is only a push module? This new project will get merged back into<br>
>>> the<br>
>>> main project when we have our complete modularizations.<br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
</div></div><div class="im HOEnZb">--<br>
Summers Pittman<br>
>>Phone:404 941 4698<br>
>>Java is my crack.<br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></blockquote></div><br></div>