They are welcome to use it as they see fit, though the only things that
should be there is the push notification stuff, the rest is my problem
:)
On 22 Jan 2016, at 12:51, Anton Hughes wrote:
Thanks Rob - really appreciate this.
May I recommend that this is published on the aerogear website. This
kind
of knowledge is gained through hard knocks. It can save many others
the
same pain.
On Fri, Jan 22, 2016 at 1:22 PM, Rob Willett
<rob.aerogear(a)robertwillett.com
> wrote:
> Anton,
>
> Its difficult to do some things without a phone, you can certainly
> develop on Cordova and get a long way on screens designs,
> controllers,
> services, posting to and getting stuff from servers but somethings
> need
> a hardware device.
>
> Off the top of my head things that don’t work properly on
> iPhone/Android simulators or at all.
>
> 1. Background processing. JavaScript timers continue to work in the
> background but do not on a real phone. Sounds innocuous but its a
> massive hassle for us.
> 2. GPS is very limited on the iPhone emulator. You can set simple GPS
> routes up and thats it. The genymotion has a GPS on off switch to
> save a
> position, useful for very, very limited uses.
> 3. No notifications on the iPhone emulator. Zilch. You can get them
> on
> the Genymotion with the link I posted.
> 4. No In-App purchasing on the iPhone. No access to the sandbox, its
> a
> nightmare even on a real phone. No idea on Android as we have up on
> the
> iPhone.
> 5. Some weird effects of different versions of IOS and background
> processing with geolocation and posting to servers with ATS. We
> can’t
> work it out at all, so we use real phones.
>
> You can get so far without a phone but at the end of the day you will
> need one to develop and test. There is no getting away from it. Ups
> cannot develop and simply deploy and hope it all works. Emulators
> will
> work, but not with any success for at least the things I’ve quoted
> above.
>
> Rob
>
> On 22 Jan 2016, at 12:10, Anton Hughes wrote:
>
>> Thanks Rob
>> On Fri, Jan 22, 2016 at 12:59 PM, Rob Willett <
>> rob.aerogear(a)robertwillett.com> wrote:
>>
>>> Unclear as to why deploying to a real device is such a problem, we
>>> develop on iPhone and Android using Cordova and even though I like
>>> the
>>> iPhone, the development and debugging tools on a real Android
>>> device
>>> are
>>> excellent and fast. When we have a real problem, we tend to ignore
>>> Xcode
>>> and Safari and the iPhone and debug it on a real Android device. We
>>> don’t have any real issues, though we always want things to be
>>> quicker.
>>>
>>
>> Its a problem for me as I dont have a cell phone - seriously.
>> But, it just sounds odd, to have to deploy and install on a new
>> piece
>> of
>> hardware each time you want to test. My usual workflow would be to
>> develop
>> locally, then when things are working, then deploy.
>>
>> And, for now, I am just doing a proof of concept - my goal is just
>> to
>> prove
>> that it is possible to send a push notification from UPS to android
>> using
>> cordova. I'm surprised at how complicated it is. But I suppose my
>> confusion
>> and frustration is simply because I am new to this style of
>> developing.
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-users
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-users
>
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users