sms,MMS, and Push Notificstions

[ELS prothero via use-livecode]

I’m curious. Has anybody done much with push notifications on mobile? There is 
a lesson on the livecode web site which is quite detailed, but leaves out the 
server side of the equation. I have been thinking about an emergency alert app 
and am exploring how difficult it would be to implement various communication 
technologies. Texts seem pretty straighforward, but I was thinking that push 
notifications might get more attention.

The goal is to get the information to the recipient’s brain. It can get to the 
device, but unless the last (weak link) is traversed, the alert is ineffective. 
The target time for this is 15 minutes.

I’ve Googled the heck out of these topics and there are really nice expensive 
services that can do the job, but we don’t want to pay the high fees. Others 
are marketing oriented, not optimized for emergency services. A custom app 
could be ideal, especially with increasing wildfire activity worldwide.

Ideas and info?
Best,
Bill

William Prothero, PhD
Professor Emeritus
University of California, Santa Barbara
http://earthlearningsolutions.org

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Simon Smith via use-livecode]

I would look at push notifications. onesignal.com looks quiet good, just
not had a chance to play with it yet.

I have found that SMS messages are too unreliable when it comes to
emergency notifications, sometimes they come through, sometimes they don't
and sometimes they come through an hour or so later.

Simon


Carpe diem

*Simon Smith*
m. +27 83 306 7862

On Mon, Aug 14, 2017 at 9:19 PM, ELS prothero via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I’m curious. Has anybody done much with push notifications on mobile?
> There is a lesson on the livecode web site which is quite detailed, but
> leaves out the server side of the equation. I have been thinking about an
> emergency alert app and am exploring how difficult it would be to implement
> various communication technologies. Texts seem pretty straighforward, but I
> was thinking that push notifications might get more attention.
>
> The goal is to get the information to the recipient’s brain. It can get to
> the device, but unless the last (weak link) is traversed, the alert is
> ineffective. The target time for this is 15 minutes.
>
> I’ve Googled the heck out of these topics and there are really nice
> expensive services that can do the job, but we don’t want to pay the high
> fees. Others are marketing oriented, not optimized for emergency services.
> A custom app could be ideal, especially with increasing wildfire activity
> worldwide.
>
> Ideas and info?
> Best,
> Bill
>
> William Prothero, PhD
> Professor Emeritus
> University of California, Santa Barbara
> http://earthlearningsolutions.org
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[William Prothero via use-livecode]

Thanks. Looks interesting. It also looks like I'd have to learn a lot to get it 
implemented. I’ve been using cURL to access an API for water meter readings, 
and it’s painful, but would probably get easier.

This looks like a good provider, tho.
Best,
Bill P

> On Aug 14, 2017, at 1:42 PM, Simon Smith via use-livecode 
>  wrote:
> 
> I would look at push notifications. onesignal.com looks quiet good, just
> not had a chance to play with it yet.
> 
> I have found that SMS messages are too unreliable when it comes to
> emergency notifications, sometimes they come through, sometimes they don't
> and sometimes they come through an hour or so later.
> 
> Simon
> 
> 
> Carpe diem
> 
> *Simon Smith*
> m. +27 83 306 7862
> 
> On Mon, Aug 14, 2017 at 9:19 PM, ELS prothero via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> I’m curious. Has anybody done much with push notifications on mobile?
>> There is a lesson on the livecode web site which is quite detailed, but
>> leaves out the server side of the equation. I have been thinking about an
>> emergency alert app and am exploring how difficult it would be to implement
>> various communication technologies. Texts seem pretty straighforward, but I
>> was thinking that push notifications might get more attention.
>> 
>> The goal is to get the information to the recipient’s brain. It can get to
>> the device, but unless the last (weak link) is traversed, the alert is
>> ineffective. The target time for this is 15 minutes.
>> 
>> I’ve Googled the heck out of these topics and there are really nice
>> expensive services that can do the job, but we don’t want to pay the high
>> fees. Others are marketing oriented, not optimized for emergency services.
>> A custom app could be ideal, especially with increasing wildfire activity
>> worldwide.
>> 
>> Ideas and info?
>> Best,
>> Bill
>> 
>> William Prothero, PhD
>> Professor Emeritus
>> University of California, Santa Barbara
>> http://earthlearningsolutions.org
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Stephen Barncard via use-livecode]

If I were to create an emergency alert app, I'd make something that stayed
alive and was always verifying the existence of a central entity - web
site, server etc. and the fail safe is that the user would be alerted when
out of range.   An 'always on' executable that would have to be carefully
crafted to not take up too much battery energy, yet ping headquarters for a
change every few seconds, then go into alert mode when the latest check
reveals the emergency.

It would be part of the routine of the wearer (fireman, whatever) to 'check
in' with the server and verify correct operation, then just keep it running
all day. The data would be minimal and UDP packets have incredibly low
latency - even a voice alert could be sent real time - VOIP.

I have no idea how the power usage would be handled in that case - the
continuous  pinging could drain the battery too quickly depending on how
it's done. But there is the challenge!

--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org

On Mon, Aug 14, 2017 at 3:25 PM, William Prothero via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Thanks. Looks interesting. It also looks like I'd have to learn a lot to
> get it implemented. I’ve been using cURL to access an API for water meter
> readings, and it’s painful, but would probably get easier.
>
> This looks like a good provider, tho.
> Best,
> Bill P
>
> > On Aug 14, 2017, at 1:42 PM, Simon Smith via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > I would look at push notifications. onesignal.com looks quiet good, just
> > not had a chance to play with it yet.
> >
> > I have found that SMS messages are too unreliable when it comes to
> > emergency notifications, sometimes they come through, sometimes they
> don't
> > and sometimes they come through an hour or so later.
> >
> > Simon
> >
> >
> > Carpe diem
> >
> > *Simon Smith*
> > m. +27 83 306 7862
> >
> > On Mon, Aug 14, 2017 at 9:19 PM, ELS prothero via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> I’m curious. Has anybody done much with push notifications on mobile?
> >> There is a lesson on the livecode web site which is quite detailed, but
> >> leaves out the server side of the equation. I have been thinking about
> an
> >> emergency alert app and am exploring how difficult it would be to
> implement
> >> various communication technologies. Texts seem pretty straighforward,
> but I
> >> was thinking that push notifications might get more attention.
> >>
> >> The goal is to get the information to the recipient’s brain. It can get
> to
> >> the device, but unless the last (weak link) is traversed, the alert is
> >> ineffective. The target time for this is 15 minutes.
> >>
> >> I’ve Googled the heck out of these topics and there are really nice
> >> expensive services that can do the job, but we don’t want to pay the
> high
> >> fees. Others are marketing oriented, not optimized for emergency
> services.
> >> A custom app could be ideal, especially with increasing wildfire
> activity
> >> worldwide.
> >>
> >> Ideas and info?
> >> Best,
> >> Bill
> >>
> >> William Prothero, PhD
> >> Professor Emeritus
> >> University of California, Santa Barbara
> >> http://earthlearningsolutions.org
> >>
> >> ___
> >> use-livecode mailing list
> >> use-livecode@lists.runrev.com
> >> Please visit this url to subscribe, unsubscribe and manage your
> >> subscription preferences:
> >> http://lists.runrev.com/mailman/listinfo/use-livecode
> > ___
> > use-livecode mailing list
> > use-livecode@lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[William Prothero via use-livecode]

Thanks, Stephen:
What we are using as a preliminary solution is a mass sms and/or MMS texts and 
identical voice calls to our 49 numbers, initiated by one of several possible 
initiators who are called if a fire is observed. We are using eztexting.com 
 for the texts and voiceshot.com  
for the voice messaging. It’s very inexpensive for voice $9/mo and 12c for each 
call. The texts are low cost too. We can enter several preset messages that we 
can choose from, depending on the immediacy of action that’s required. So, I 
figure that there are two tries per event and we should get most of the folks. 
I think another alert channel would be push notifications, but for now we’re 
sticking with voice and text. We expect the alerts to be very rare (we hope). I 
think a custom app that could initiate these actions more automatically would 
be quite nice, but the IT for it would take more of an investment than I’m 
willing to make, and there is no money in it unless it would take off in the 
app store, and if I made it general enough for most neighborhoods.

For a bare bones, primitive system, text messages could be sent out and 
initiating a voice call to the group voice provider could be built in. It has 
to be easy and fast for the alert initiator, who would most likely be packing 
up for evacuation at the same time. Push notifications would be nice too. One 
problem is that the initiator’s phone number always appears in the voice call 
and text notification. If a more descriptive sender, like “ALERT-XX”, it would 
be better, but that would most likely require setting up a dedicated alert 
server, and I don’t want to tackle that at this time.

Best,
Bill P.

> On Aug 14, 2017, at 4:18 PM, Stephen Barncard via use-livecode 
>  wrote:
> 
> If I were to create an emergency alert app, I'd make something that stayed
> alive and was always verifying the existence of a central entity - web
> site, server etc. and the fail safe is that the user would be alerted when
> out of range.   An 'always on' executable that would have to be carefully
> crafted to not take up too much battery energy, yet ping headquarters for a
> change every few seconds, then go into alert mode when the latest check
> reveals the emergency.
> 
> It would be part of the routine of the wearer (fireman, whatever) to 'check
> in' with the server and verify correct operation, then just keep it running
> all day. The data would be minimal and UDP packets have incredibly low
> latency - even a voice alert could be sent real time - VOIP.
> 
> I have no idea how the power usage would be handled in that case - the
> continuous  pinging could drain the battery too quickly depending on how
> it's done. But there is the challenge!
> 
> --
> Stephen Barncard - Sebastopol Ca. USA -
> mixstream.org
> 
> On Mon, Aug 14, 2017 at 3:25 PM, William Prothero via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> Thanks. Looks interesting. It also looks like I'd have to learn a lot to
>> get it implemented. I’ve been using cURL to access an API for water meter
>> readings, and it’s painful, but would probably get easier.
>> 
>> This looks like a good provider, tho.
>> Best,
>> Bill P
>> 
>>> On Aug 14, 2017, at 1:42 PM, Simon Smith via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>> 
>>> I would look at push notifications. onesignal.com looks quiet good, just
>>> not had a chance to play with it yet.
>>> 
>>> I have found that SMS messages are too unreliable when it comes to
>>> emergency notifications, sometimes they come through, sometimes they
>> don't
>>> and sometimes they come through an hour or so later.
>>> 
>>> Simon
>>> 
>>> 
>>> Carpe diem
>>> 
>>> *Simon Smith*
>>> m. +27 83 306 7862
>>> 
>>> On Mon, Aug 14, 2017 at 9:19 PM, ELS prothero via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
 I’m curious. Has anybody done much with push notifications on mobile?
 There is a lesson on the livecode web site which is quite detailed, but
 leaves out the server side of the equation. I have been thinking about
>> an
 emergency alert app and am exploring how difficult it would be to
>> implement
 various communication technologies. Texts seem pretty straighforward,
>> but I
 was thinking that push notifications might get more attention.
 
 The goal is to get the information to the recipient’s brain. It can get
>> to
 the device, but unless the last (weak link) is traversed, the alert is
 ineffective. The target time for this is 15 minutes.
 
 I’ve Googled the heck out of these topics and there are really nice
 expensive services that can do the job, but we don’t want to pay the
>> high
 fees. Others are marketing oriented, not optimized for emergency
>> services.
 A custom app could be ideal, especially with increasing wildfire
>> activity
 worldwide.
 
 Ideas and info?
 Best,
 Bill
 
 William Prothe

Re: sms,MMS, and Push Notificstions

[Mike Kerner via use-livecode]

app push is pretty easy/straightforward in LC, but there are multiple QR's
out to add features/fix things on them.

On Mon, Aug 14, 2017 at 11:01 PM, William Prothero via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Thanks, Stephen:
> What we are using as a preliminary solution is a mass sms and/or MMS texts
> and identical voice calls to our 49 numbers, initiated by one of several
> possible initiators who are called if a fire is observed. We are using
> eztexting.com  for the texts and voiceshot.com <
> http://voiceshot.com/> for the voice messaging. It’s very inexpensive for
> voice $9/mo and 12c for each call. The texts are low cost too. We can enter
> several preset messages that we can choose from, depending on the immediacy
> of action that’s required. So, I figure that there are two tries per event
> and we should get most of the folks. I think another alert channel would be
> push notifications, but for now we’re sticking with voice and text. We
> expect the alerts to be very rare (we hope). I think a custom app that
> could initiate these actions more automatically would be quite nice, but
> the IT for it would take more of an investment than I’m willing to make,
> and there is no money in it unless it would take off in the app store, and
> if I made it general enough for most neighborhoods.
>
> For a bare bones, primitive system, text messages could be sent out and
> initiating a voice call to the group voice provider could be built in. It
> has to be easy and fast for the alert initiator, who would most likely be
> packing up for evacuation at the same time. Push notifications would be
> nice too. One problem is that the initiator’s phone number always appears
> in the voice call and text notification. If a more descriptive sender, like
> “ALERT-XX”, it would be better, but that would most likely require setting
> up a dedicated alert server, and I don’t want to tackle that at this time.
>
> Best,
> Bill P.
>
> > On Aug 14, 2017, at 4:18 PM, Stephen Barncard via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > If I were to create an emergency alert app, I'd make something that
> stayed
> > alive and was always verifying the existence of a central entity - web
> > site, server etc. and the fail safe is that the user would be alerted
> when
> > out of range.   An 'always on' executable that would have to be carefully
> > crafted to not take up too much battery energy, yet ping headquarters
> for a
> > change every few seconds, then go into alert mode when the latest check
> > reveals the emergency.
> >
> > It would be part of the routine of the wearer (fireman, whatever) to
> 'check
> > in' with the server and verify correct operation, then just keep it
> running
> > all day. The data would be minimal and UDP packets have incredibly low
> > latency - even a voice alert could be sent real time - VOIP.
> >
> > I have no idea how the power usage would be handled in that case - the
> > continuous  pinging could drain the battery too quickly depending on how
> > it's done. But there is the challenge!
> >
> > --
> > Stephen Barncard - Sebastopol Ca. USA -
> > mixstream.org
> >
> > On Mon, Aug 14, 2017 at 3:25 PM, William Prothero via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> Thanks. Looks interesting. It also looks like I'd have to learn a lot to
> >> get it implemented. I’ve been using cURL to access an API for water
> meter
> >> readings, and it’s painful, but would probably get easier.
> >>
> >> This looks like a good provider, tho.
> >> Best,
> >> Bill P
> >>
> >>> On Aug 14, 2017, at 1:42 PM, Simon Smith via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>>
> >>> I would look at push notifications. onesignal.com looks quiet good,
> just
> >>> not had a chance to play with it yet.
> >>>
> >>> I have found that SMS messages are too unreliable when it comes to
> >>> emergency notifications, sometimes they come through, sometimes they
> >> don't
> >>> and sometimes they come through an hour or so later.
> >>>
> >>> Simon
> >>>
> >>>
> >>> Carpe diem
> >>>
> >>> *Simon Smith*
> >>> m. +27 83 306 7862
> >>>
> >>> On Mon, Aug 14, 2017 at 9:19 PM, ELS prothero via use-livecode <
> >>> use-livecode@lists.runrev.com> wrote:
> >>>
>  I’m curious. Has anybody done much with push notifications on mobile?
>  There is a lesson on the livecode web site which is quite detailed,
> but
>  leaves out the server side of the equation. I have been thinking about
> >> an
>  emergency alert app and am exploring how difficult it would be to
> >> implement
>  various communication technologies. Texts seem pretty straighforward,
> >> but I
>  was thinking that push notifications might get more attention.
> 
>  The goal is to get the information to the recipient’s brain. It can
> get
> >> to
>  the device, but unless the last (weak link) is traversed, the alert is
>  ineffective. The target time for th

Re: sms,MMS, and Push Notificstions

[prothero--- via use-livecode]

My big question at this point is what is required on the server side? I looked 
at onesignal, which looks like a really nice API provider, but I need to be 
able to allocate a load of time to learn the various ways of accessing it, like 
REST, cURL, etc. I'm stumbling around now with those technologies, but will 
have to make a more systematic learning effort if I am going to proceed in that 
direction.

Best,
Bill

William Prothero
http://es.earthednet.org

> On Aug 15, 2017, at 7:42 AM, Mike Kerner via use-livecode 
>  wrote:
> 
> app push is pretty easy/straightforward in LC, but there are multiple QR's
> out to add features/fix things on them.
> 
> On Mon, Aug 14, 2017 at 11:01 PM, William Prothero via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> Thanks, Stephen:
>> What we are using as a preliminary solution is a mass sms and/or MMS texts
>> and identical voice calls to our 49 numbers, initiated by one of several
>> possible initiators who are called if a fire is observed. We are using
>> eztexting.com  for the texts and voiceshot.com <
>> http://voiceshot.com/> for the voice messaging. It’s very inexpensive for
>> voice $9/mo and 12c for each call. The texts are low cost too. We can enter
>> several preset messages that we can choose from, depending on the immediacy
>> of action that’s required. So, I figure that there are two tries per event
>> and we should get most of the folks. I think another alert channel would be
>> push notifications, but for now we’re sticking with voice and text. We
>> expect the alerts to be very rare (we hope). I think a custom app that
>> could initiate these actions more automatically would be quite nice, but
>> the IT for it would take more of an investment than I’m willing to make,
>> and there is no money in it unless it would take off in the app store, and
>> if I made it general enough for most neighborhoods.
>> 
>> For a bare bones, primitive system, text messages could be sent out and
>> initiating a voice call to the group voice provider could be built in. It
>> has to be easy and fast for the alert initiator, who would most likely be
>> packing up for evacuation at the same time. Push notifications would be
>> nice too. One problem is that the initiator’s phone number always appears
>> in the voice call and text notification. If a more descriptive sender, like
>> “ALERT-XX”, it would be better, but that would most likely require setting
>> up a dedicated alert server, and I don’t want to tackle that at this time.
>> 
>> Best,
>> Bill P.
>> 
>>> On Aug 14, 2017, at 4:18 PM, Stephen Barncard via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>> 
>>> If I were to create an emergency alert app, I'd make something that
>> stayed
>>> alive and was always verifying the existence of a central entity - web
>>> site, server etc. and the fail safe is that the user would be alerted
>> when
>>> out of range.   An 'always on' executable that would have to be carefully
>>> crafted to not take up too much battery energy, yet ping headquarters
>> for a
>>> change every few seconds, then go into alert mode when the latest check
>>> reveals the emergency.
>>> 
>>> It would be part of the routine of the wearer (fireman, whatever) to
>> 'check
>>> in' with the server and verify correct operation, then just keep it
>> running
>>> all day. The data would be minimal and UDP packets have incredibly low
>>> latency - even a voice alert could be sent real time - VOIP.
>>> 
>>> I have no idea how the power usage would be handled in that case - the
>>> continuous  pinging could drain the battery too quickly depending on how
>>> it's done. But there is the challenge!
>>> 
>>> --
>>> Stephen Barncard - Sebastopol Ca. USA -
>>> mixstream.org
>>> 
>>> On Mon, Aug 14, 2017 at 3:25 PM, William Prothero via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
 Thanks. Looks interesting. It also looks like I'd have to learn a lot to
 get it implemented. I’ve been using cURL to access an API for water
>> meter
 readings, and it’s painful, but would probably get easier.
 
 This looks like a good provider, tho.
 Best,
 Bill P
 
> On Aug 14, 2017, at 1:42 PM, Simon Smith via use-livecode <
 use-livecode@lists.runrev.com> wrote:
> 
> I would look at push notifications. onesignal.com looks quiet good,
>> just
> not had a chance to play with it yet.
> 
> I have found that SMS messages are too unreliable when it comes to
> emergency notifications, sometimes they come through, sometimes they
 don't
> and sometimes they come through an hour or so later.
> 
> Simon
> 
> 
> Carpe diem
> 
> *Simon Smith*
> m. +27 83 306 7862
> 
> On Mon, Aug 14, 2017 at 9:19 PM, ELS prothero via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> I’m curious. Has anybody done much with push notifications on mobile?
>> There is a lesson

Re: sms,MMS, and Push Notificstions

[Mike Kerner via use-livecode]

There is a LC stack that John wrote that you can use.

On Tue, Aug 15, 2017 at 11:13 AM, prothero--- via use-livecode <
use-livecode@lists.runrev.com> wrote:

> My big question at this point is what is required on the server side? I
> looked at onesignal, which looks like a really nice API provider, but I
> need to be able to allocate a load of time to learn the various ways of
> accessing it, like REST, cURL, etc. I'm stumbling around now with those
> technologies, but will have to make a more systematic learning effort if I
> am going to proceed in that direction.
>
> Best,
> Bill
>
> William Prothero
> http://es.earthednet.org
>
> > On Aug 15, 2017, at 7:42 AM, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > app push is pretty easy/straightforward in LC, but there are multiple
> QR's
> > out to add features/fix things on them.
> >
> > On Mon, Aug 14, 2017 at 11:01 PM, William Prothero via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> Thanks, Stephen:
> >> What we are using as a preliminary solution is a mass sms and/or MMS
> texts
> >> and identical voice calls to our 49 numbers, initiated by one of several
> >> possible initiators who are called if a fire is observed. We are using
> >> eztexting.com  for the texts and voiceshot.com <
> >> http://voiceshot.com/> for the voice messaging. It’s very inexpensive
> for
> >> voice $9/mo and 12c for each call. The texts are low cost too. We can
> enter
> >> several preset messages that we can choose from, depending on the
> immediacy
> >> of action that’s required. So, I figure that there are two tries per
> event
> >> and we should get most of the folks. I think another alert channel
> would be
> >> push notifications, but for now we’re sticking with voice and text. We
> >> expect the alerts to be very rare (we hope). I think a custom app that
> >> could initiate these actions more automatically would be quite nice, but
> >> the IT for it would take more of an investment than I’m willing to make,
> >> and there is no money in it unless it would take off in the app store,
> and
> >> if I made it general enough for most neighborhoods.
> >>
> >> For a bare bones, primitive system, text messages could be sent out and
> >> initiating a voice call to the group voice provider could be built in.
> It
> >> has to be easy and fast for the alert initiator, who would most likely
> be
> >> packing up for evacuation at the same time. Push notifications would be
> >> nice too. One problem is that the initiator’s phone number always
> appears
> >> in the voice call and text notification. If a more descriptive sender,
> like
> >> “ALERT-XX”, it would be better, but that would most likely require
> setting
> >> up a dedicated alert server, and I don’t want to tackle that at this
> time.
> >>
> >> Best,
> >> Bill P.
> >>
> >>> On Aug 14, 2017, at 4:18 PM, Stephen Barncard via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>>
> >>> If I were to create an emergency alert app, I'd make something that
> >> stayed
> >>> alive and was always verifying the existence of a central entity - web
> >>> site, server etc. and the fail safe is that the user would be alerted
> >> when
> >>> out of range.   An 'always on' executable that would have to be
> carefully
> >>> crafted to not take up too much battery energy, yet ping headquarters
> >> for a
> >>> change every few seconds, then go into alert mode when the latest check
> >>> reveals the emergency.
> >>>
> >>> It would be part of the routine of the wearer (fireman, whatever) to
> >> 'check
> >>> in' with the server and verify correct operation, then just keep it
> >> running
> >>> all day. The data would be minimal and UDP packets have incredibly low
> >>> latency - even a voice alert could be sent real time - VOIP.
> >>>
> >>> I have no idea how the power usage would be handled in that case - the
> >>> continuous  pinging could drain the battery too quickly depending on
> how
> >>> it's done. But there is the challenge!
> >>>
> >>> --
> >>> Stephen Barncard - Sebastopol Ca. USA -
> >>> mixstream.org
> >>>
> >>> On Mon, Aug 14, 2017 at 3:25 PM, William Prothero via use-livecode <
> >>> use-livecode@lists.runrev.com> wrote:
> >>>
>  Thanks. Looks interesting. It also looks like I'd have to learn a lot
> to
>  get it implemented. I’ve been using cURL to access an API for water
> >> meter
>  readings, and it’s painful, but would probably get easier.
> 
>  This looks like a good provider, tho.
>  Best,
>  Bill P
> 
> > On Aug 14, 2017, at 1:42 PM, Simon Smith via use-livecode <
>  use-livecode@lists.runrev.com> wrote:
> >
> > I would look at push notifications. onesignal.com looks quiet good,
> >> just
> > not had a chance to play with it yet.
> >
> > I have found that SMS messages are too unreliable when it comes to
> > emergency notifications, sometimes they come through, sometimes they
> 

Re: sms,MMS, and Push Notificstions

[prothero--- via use-livecode]

I've checked out the very nice lesson that refers to John's stack. I'll check 
it out.

Thanks for the reminder. The lesson rested the alert system by simulating the 
server, so I incorrectly got confused about the lack of info or reference to 
the server.
Best,
Bill P

William Prothero
http://es.earthednet.org

> On Aug 15, 2017, at 8:28 AM, Mike Kerner via use-livecode 
>  wrote:
> 
> There is a LC stack that John wrote that you can use.
> 
> On Tue, Aug 15, 2017 at 11:13 AM, prothero--- via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> My big question at this point is what is required on the server side? I
>> looked at onesignal, which looks like a really nice API provider, but I
>> need to be able to allocate a load of time to learn the various ways of
>> accessing it, like REST, cURL, etc. I'm stumbling around now with those
>> technologies, but will have to make a more systematic learning effort if I
>> am going to proceed in that direction.
>> 
>> Best,
>> Bill
>> 
>> William Prothero
>> http://es.earthednet.org
>> 
>>> On Aug 15, 2017, at 7:42 AM, Mike Kerner via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>> 
>>> app push is pretty easy/straightforward in LC, but there are multiple
>> QR's
>>> out to add features/fix things on them.
>>> 
>>> On Mon, Aug 14, 2017 at 11:01 PM, William Prothero via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
 Thanks, Stephen:
 What we are using as a preliminary solution is a mass sms and/or MMS
>> texts
 and identical voice calls to our 49 numbers, initiated by one of several
 possible initiators who are called if a fire is observed. We are using
 eztexting.com  for the texts and voiceshot.com <
 http://voiceshot.com/> for the voice messaging. It’s very inexpensive
>> for
 voice $9/mo and 12c for each call. The texts are low cost too. We can
>> enter
 several preset messages that we can choose from, depending on the
>> immediacy
 of action that’s required. So, I figure that there are two tries per
>> event
 and we should get most of the folks. I think another alert channel
>> would be
 push notifications, but for now we’re sticking with voice and text. We
 expect the alerts to be very rare (we hope). I think a custom app that
 could initiate these actions more automatically would be quite nice, but
 the IT for it would take more of an investment than I’m willing to make,
 and there is no money in it unless it would take off in the app store,
>> and
 if I made it general enough for most neighborhoods.
 
 For a bare bones, primitive system, text messages could be sent out and
 initiating a voice call to the group voice provider could be built in.
>> It
 has to be easy and fast for the alert initiator, who would most likely
>> be
 packing up for evacuation at the same time. Push notifications would be
 nice too. One problem is that the initiator’s phone number always
>> appears
 in the voice call and text notification. If a more descriptive sender,
>> like
 “ALERT-XX”, it would be better, but that would most likely require
>> setting
 up a dedicated alert server, and I don’t want to tackle that at this
>> time.
 
 Best,
 Bill P.
 
> On Aug 14, 2017, at 4:18 PM, Stephen Barncard via use-livecode <
 use-livecode@lists.runrev.com> wrote:
> 
> If I were to create an emergency alert app, I'd make something that
 stayed
> alive and was always verifying the existence of a central entity - web
> site, server etc. and the fail safe is that the user would be alerted
 when
> out of range.   An 'always on' executable that would have to be
>> carefully
> crafted to not take up too much battery energy, yet ping headquarters
 for a
> change every few seconds, then go into alert mode when the latest check
> reveals the emergency.
> 
> It would be part of the routine of the wearer (fireman, whatever) to
 'check
> in' with the server and verify correct operation, then just keep it
 running
> all day. The data would be minimal and UDP packets have incredibly low
> latency - even a voice alert could be sent real time - VOIP.
> 
> I have no idea how the power usage would be handled in that case - the
> continuous  pinging could drain the battery too quickly depending on
>> how
> it's done. But there is the challenge!
> 
> --
> Stephen Barncard - Sebastopol Ca. USA -
> mixstream.org
> 
> On Mon, Aug 14, 2017 at 3:25 PM, William Prothero via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> Thanks. Looks interesting. It also looks like I'd have to learn a lot
>> to
>> get it implemented. I’ve been using cURL to access an API for water
 meter
>> readings, and it’s painful, but would probably get easier.
>> 
>> This looks like a good provider, tho.

Re: sms,MMS, and Push Notificstions

[William Prothero via use-livecode]

Mike:
Hmm… I downloaded APNsAssistant, which is linked to the lesson. Is this the one 
that you modified and re-posted to gitHub?

A quick perusal of that stack, it looks like he uses a shell command to 
simulate the sending of an alert. Is that how a notification is intended to be 
sent, or is this method only for testing? If a notification could be initiated 
from the app, it would eliminate the need for a server, except to store the 
receiver information/tokens/whatever is needed. That would be preferable. But …?

So, sorry for seeming dense, but I’m confused over the role of the “server”. 
Whether a service like onesignal is required to distribute push notifications, 
or whether the initiator app can just get the info from some database and send 
the notifications from the app directly without activating some network server 
api that does the sending.

Best,
Bill P

> On Aug 15, 2017, at 8:28 AM, Mike Kerner via use-livecode 
>  wrote:
> 
> There is a LC stack that John wrote that you can use.
> 
> On Tue, Aug 15, 2017 at 11:13 AM, prothero--- via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> My big question at this point is what is required on the server side? I
>> looked at onesignal, which looks like a really nice API provider, but I
>> need to be able to allocate a load of time to learn the various ways of
>> accessing it, like REST, cURL, etc. I'm stumbling around now with those
>> technologies, but will have to make a more systematic learning effort if I
>> am going to proceed in that direction.
>> 
>> Best,
>> Bill
>> 
>> William Prothero
>> http://es.earthednet.org
>> 
>>> On Aug 15, 2017, at 7:42 AM, Mike Kerner via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>> 
>>> app push is pretty easy/straightforward in LC, but there are multiple
>> QR's
>>> out to add features/fix things on them.
>>> 
>>> On Mon, Aug 14, 2017 at 11:01 PM, William Prothero via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
 Thanks, Stephen:
 What we are using as a preliminary solution is a mass sms and/or MMS
>> texts
 and identical voice calls to our 49 numbers, initiated by one of several
 possible initiators who are called if a fire is observed. We are using
 eztexting.com  for the texts and voiceshot.com <
 http://voiceshot.com/> for the voice messaging. It’s very inexpensive
>> for
 voice $9/mo and 12c for each call. The texts are low cost too. We can
>> enter
 several preset messages that we can choose from, depending on the
>> immediacy
 of action that’s required. So, I figure that there are two tries per
>> event
 and we should get most of the folks. I think another alert channel
>> would be
 push notifications, but for now we’re sticking with voice and text. We
 expect the alerts to be very rare (we hope). I think a custom app that
 could initiate these actions more automatically would be quite nice, but
 the IT for it would take more of an investment than I’m willing to make,
 and there is no money in it unless it would take off in the app store,
>> and
 if I made it general enough for most neighborhoods.
 
 For a bare bones, primitive system, text messages could be sent out and
 initiating a voice call to the group voice provider could be built in.
>> It
 has to be easy and fast for the alert initiator, who would most likely
>> be
 packing up for evacuation at the same time. Push notifications would be
 nice too. One problem is that the initiator’s phone number always
>> appears
 in the voice call and text notification. If a more descriptive sender,
>> like
 “ALERT-XX”, it would be better, but that would most likely require
>> setting
 up a dedicated alert server, and I don’t want to tackle that at this
>> time.
 
 Best,
 Bill P.
 
> On Aug 14, 2017, at 4:18 PM, Stephen Barncard via use-livecode <
 use-livecode@lists.runrev.com> wrote:
> 
> If I were to create an emergency alert app, I'd make something that
 stayed
> alive and was always verifying the existence of a central entity - web
> site, server etc. and the fail safe is that the user would be alerted
 when
> out of range.   An 'always on' executable that would have to be
>> carefully
> crafted to not take up too much battery energy, yet ping headquarters
 for a
> change every few seconds, then go into alert mode when the latest check
> reveals the emergency.
> 
> It would be part of the routine of the wearer (fireman, whatever) to
 'check
> in' with the server and verify correct operation, then just keep it
 running
> all day. The data would be minimal and UDP packets have incredibly low
> latency - even a voice alert could be sent real time - VOIP.
> 
> I have no idea how the power usage would be handled in that case - the
> continuous  pinging could drain the battery too quickly dep

Re: sms,MMS, and Push Notificstions

[Andrew Bell via use-livecode]

I recently tackled push notifications for a client project that was  
WAY more in-depth than I imagined (and initially quoted for). Using  
the LC tutorials for push notifications with APNsAssistant and  
AnroidGCM I was able to add push notification sending from a  
standalone desktop app created entirely in LC to a mobile app also  
created entirely in LC.


The most difficult element was collecting and maintaining all the  
unique push IDs from end users of the mobile app that is being  
communicated to. I have the mobile app "phone home" with that push id  
(pushNotificationReceived) and add an entry in a remote database on a  
LC server by way of the super-helpful API provided by HostM. The  
desktop app queries the database for unique IDs of users and looks at  
the length of the push ID to determine if it is iOS or Google  
(couldn't find definitive documentation on the format of these IDs,  
but iOS has < and > symbols and is considerably shorter than  
Android IDs) then references the appropriate code base to format and  
send the message (iOS has a header and payload, Android has a header  
and sub-header and playload).


This is a shotgun approach that inevitably attempts to send more  
notifications than there are actual users because I have discovered  
that these IDs seem to change over time (not sure when or why). I see  
this as a no harm/no foul approach because each device can only have 1  
unique ID per app, so some of the messages get transmitted but never  
received. Android returns an error message in the JSON for each  
attempt flagging it as successful or not, iOS does not.


I was able to get Unicode emoji support in the messages, but have a  
real half-ass method of entering them right now that I intend to  
update at some point. Currently I have a browser widget that loads a  
third-party webpage of emojis (emojipedia.org) that needs to be copied  
and pasted into a text field... but the website uses a copy button to  
truly copy that doesn't work in my standalone so I have instructed my  
end-user to select the emoji from that browser widget and  
right-click/ctrl-click to copy to the clipboard and paste into the  
field.


--Andrew Bell



Mike:
Hmm? I downloaded APNsAssistant, which is linked to the lesson. Is  
this the one that you modified and re-posted to gitHub?


A quick perusal of that stack, it looks like he uses a shell command  
to simulate the sending of an alert. Is that how a notification is  
intended to be sent, or is this method only for testing? If a  
notification could be initiated from the app, it would eliminate the  
need for a server, except to store the receiver  
information/tokens/whatever is needed. That would be preferable. But  
??


So, sorry for seeming dense, but I?m confused over the role of the  
?server?. Whether a service like onesignal is required to distribute  
push notifications, or whether the initiator app can just get the  
info from some database and send the notifications from the app  
directly without activating some network server api that does the  
sending.


Best,
Bill P




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Mike Kerner via use-livecode]

You have to have the app phone home with its id.  The id is determined by
the device, and is a product of the device and the app running on it that
is to receive notifications.  You can phone home via a filesharing service,
an online db, contacting a webserver, etc.  For distinguishing between the
platforms, you can embed "the environment" in your phone home message.  The
other thing you can do (which I do) is to store the id before sending it.
Then with each launch of the app or after some other event, you check the
old id and the new one, and if it changes, phone home, again, with the old
id (presuming you don't have some other identifier tied to the app on each
device.  If you do, you can send that, instead) and the new id.  On the
desktop/server/whatever side, you update, accordingly.

Your app can also check to see if it is receiving notifications, or if
notifications are enabled, and act accordingly, including checking to see
if it has received all the notifications, and if it needs to pull any other
data, since there is no guarantee on either platform that a notification
will be delivered.

As of right now, silent notifications are not supported in LC so we have to
make do with what we have.

On Tue, Aug 15, 2017 at 12:53 PM, Andrew Bell via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I recently tackled push notifications for a client project that was WAY
> more in-depth than I imagined (and initially quoted for). Using the LC
> tutorials for push notifications with APNsAssistant and AnroidGCM I was
> able to add push notification sending from a standalone desktop app created
> entirely in LC to a mobile app also created entirely in LC.
>
> The most difficult element was collecting and maintaining all the unique
> push IDs from end users of the mobile app that is being communicated to. I
> have the mobile app "phone home" with that push id
> (pushNotificationReceived) and add an entry in a remote database on a LC
> server by way of the super-helpful API provided by HostM. The desktop app
> queries the database for unique IDs of users and looks at the length of the
> push ID to determine if it is iOS or Google (couldn't find definitive
> documentation on the format of these IDs, but iOS has < and > symbols
> and is considerably shorter than Android IDs) then references the
> appropriate code base to format and send the message (iOS has a header and
> payload, Android has a header and sub-header and playload).
>
> This is a shotgun approach that inevitably attempts to send more
> notifications than there are actual users because I have discovered that
> these IDs seem to change over time (not sure when or why). I see this as a
> no harm/no foul approach because each device can only have 1 unique ID per
> app, so some of the messages get transmitted but never received. Android
> returns an error message in the JSON for each attempt flagging it as
> successful or not, iOS does not.
>
> I was able to get Unicode emoji support in the messages, but have a real
> half-ass method of entering them right now that I intend to update at some
> point. Currently I have a browser widget that loads a third-party webpage
> of emojis (emojipedia.org) that needs to be copied and pasted into a text
> field... but the website uses a copy button to truly copy that doesn't work
> in my standalone so I have instructed my end-user to select the emoji from
> that browser widget and right-click/ctrl-click to copy to the clipboard and
> paste into the field.
>
> --Andrew Bell
>
>
> Mike:
>> Hmm? I downloaded APNsAssistant, which is linked to the lesson. Is this
>> the one that you modified and re-posted to gitHub?
>>
>> A quick perusal of that stack, it looks like he uses a shell command to
>> simulate the sending of an alert. Is that how a notification is intended to
>> be sent, or is this method only for testing? If a notification could be
>> initiated from the app, it would eliminate the need for a server, except to
>> store the receiver information/tokens/whatever is needed. That would be
>> preferable. But ??
>>
>> So, sorry for seeming dense, but I?m confused over the role of the
>> ?server?. Whether a service like onesignal is required to distribute push
>> notifications, or whether the initiator app can just get the info from some
>> database and send the notifications from the app directly without
>> activating some network server api that does the sending.
>>
>> Best,
>> Bill P
>>
>
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."

Re: sms,MMS, and Push Notificstions

[Mike Kerner via use-livecode]

You have to have the app phone home with its id.  The id is determined by
the device, and is a product of the device and the app running on it that
is to receive notifications.  You can phone home via a filesharing service,
an online db, contacting a webserver, etc.  For distinguishing between the
platforms, you can embed "the environment" in your phone home message.  The
other thing you can do (which I do) is to store the id before sending it.  Then
with each launch of the app or after some other event, you check the old id
and the new one, and if it changes, phone home, again, with the old id
(presuming you don't have some other identifier tied to the app on each
device.  If you do, you can send that, instead) and the new id.  On the
desktop/server/whatever side, you update, accordingly.

Your app can also check to see if it is receiving notifications, or if
notifications are enabled, and act accordingly, including checking to see
if it has received all the notifications, and if it needs to pull any other
data, since there is no guarantee on either platform that a notification
will be delivered.

As of right now, silent notifications are not supported in LC so we have to
make do with what we have.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Mike Kerner via use-livecode]

I got a message that one of my other messages was moderated for being too
large.  I can't see if it got delivered, or not, so in response to Bill's
question about the repo:

If you mean having the mobile do it, I hadn't thought about that.  It might
be possible with tsnet.  He is not simulating anything.  The shell command
is what is used to send the alerts.  No, you don't need to use a
third-party service, if you use this code.  Instead, you have the code
running on a machine that you control.  I have never figured out to make
the code work properly from a PC (I have never figured out how to get the
session to end and therefore for APNS to send the message, but it does work
from a Mac.
I do exactly what you are proposing - I have the stack attached to a DB
that has various device push id's.  I load them up and fire off my messages
from there.
The repo that I built has the original stack, as well as the code broken
out so it can be used as a library and therefore be submoduled, etc. with
git.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[William Prothero via use-livecode]

Thanks for all the info, Mike. I will most likely have more questions.
Best,
Bill Prothero

William A. Prothero
http://earthlearningsolution.org/

> On Aug 15, 2017, at 10:57 AM, Mike Kerner via use-livecode 
>  wrote:
> 
> I got a message that one of my other messages was moderated for being too
> large.  I can't see if it got delivered, or not, so in response to Bill's
> question about the repo:
> 
> If you mean having the mobile do it, I hadn't thought about that.  It might
> be possible with tsnet.  He is not simulating anything.  The shell command
> is what is used to send the alerts.  No, you don't need to use a
> third-party service, if you use this code.  Instead, you have the code
> running on a machine that you control.  I have never figured out to make
> the code work properly from a PC (I have never figured out how to get the
> session to end and therefore for APNS to send the message, but it does work
> from a Mac.
> I do exactly what you are proposing - I have the stack attached to a DB
> that has various device push id's.  I load them up and fire off my messages
> from there.
> The repo that I built has the original stack, as well as the code broken
> out so it can be used as a library and therefore be submoduled, etc. with
> git.
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Ben Rubinstein via use-livecode]

Just to add a +1 for OneSignal. We've used it for a couple of projects and 
it's great.


In theory you could run your own push notification server, in practise as 
Andrew noted it's a ton of work, and unless your needs are very unusual 
probably not worth it.


There are a number of commercial services, most of which actually end up quite 
expensive if you're dealing with substantial numbers of clients (but perhaps 
not so in your case); we were using one which was cheaper - until they closed 
their doors.


Then we switched to OneSignal, which is free and so far has been excellent. 
They also have an API so they may be worth using as a piece of your solution 
even if you do have outré needs - although I haven't actually worked with this 
yet.


Good luck!

Ben

On 16/08/2017 03:29, William Prothero via use-livecode wrote:

Thanks for all the info, Mike. I will most likely have more questions.
Best,
Bill Prothero

William A. Prothero
http://earthlearningsolution.org/


On Aug 15, 2017, at 10:57 AM, Mike Kerner via use-livecode 
 wrote:

I got a message that one of my other messages was moderated for being too
large.  I can't see if it got delivered, or not, so in response to Bill's
question about the repo:

If you mean having the mobile do it, I hadn't thought about that.  It might
be possible with tsnet.  He is not simulating anything.  The shell command
is what is used to send the alerts.  No, you don't need to use a
third-party service, if you use this code.  Instead, you have the code
running on a machine that you control.  I have never figured out to make
the code work properly from a PC (I have never figured out how to get the
session to end and therefore for APNS to send the message, but it does work
from a Mac.
I do exactly what you are proposing - I have the stack attached to a DB
that has various device push id's.  I load them up and fire off my messages
from there.
The repo that I built has the original stack, as well as the code broken
out so it can be used as a library and therefore be submoduled, etc. with
git.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Bob Sneidar via use-livecode]

erm... nothing is free. They must be getting something out of it. Ads at least. 
Harvesting phone numbers likely. IMHO it is a really bad idea to use free 
services in commercial projects. Even if they are innocuous, there is no 
guarantee a free service will always be there. 

Bob S


> On Aug 16, 2017, at 08:38 , Ben Rubinstein via use-livecode 
>  wrote:
> 
> Then we switched to OneSignal, which is free


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Mike Kerner via use-livecode]

I disagree with Ben on the effort of rolling your own.  The first one is
probably some work, until you understand how push works, but after you
understand, it is pretty easy.

On Wed, Aug 16, 2017 at 11:56 AM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:

> erm... nothing is free. They must be getting something out of it. Ads at
> least. Harvesting phone numbers likely. IMHO it is a really bad idea to use
> free services in commercial projects. Even if they are innocuous, there is
> no guarantee a free service will always be there.
>
> Bob S
>
>
> > On Aug 16, 2017, at 08:38 , Ben Rubinstein via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Then we switched to OneSignal, which is free
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Richard Gaskin via use-livecode]

Mike Kerner wrote:

> I disagree with Ben on the effort of rolling your own.  The first one
> is probably some work, until you understand how push works, but after
> you understand, it is pretty easy.

I don't mind learning new things, and I often prefer the control I get 
with my own private systems.


What resources would you recommend for learning more about setting up a 
notification server?


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Matthias Rebbe via use-livecode]

> Am 16.08.2017 um 20:27 schrieb Richard Gaskin via use-livecode 
> mailto:use-livecode@lists.runrev.com>>:
> 
> Mike Kerner wrote:
> 
> > I disagree with Ben on the effort of rolling your own.  The first one
> > is probably some work, until you understand how push works, but after
> > you understand, it is pretty easy.
> 
> I don't mind learning new things, and I often prefer the control I get with 
> my own private systems.
> 
> What resources would you recommend for learning more about setting up a 
> notification server?

It would be great to have  a Livecode Server solution.


Maybe this would be also a good topic for the LC Global conference?

Matthias

> 
> -- 
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> 
> ambassa...@fourthworld.com 
> http://www.FourthWorld.com 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com 
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[William Prothero via use-livecode]

Mike:
Me too on Richard’s request. I think the livecode lesson is a good start, but 
yes, setting up the server is another issue entirely. Since you’ve been through 
this process, it would be very useful to hear which learning resources you 
found most useful.

Here are a couple of promising links I found by Googling around.

This youtube video looks quite promising. It shows how to set up a server and 
the push notifications are sent using a cron job. I would bet the php code 
could be easily modified to sent the notification from a command on an app or 
mobile device.
https://youtu.be/x4swrHvBqEw 
More similar:
https://webresourcesdepot.com/easy-apns-apple-push-notifications-with-php-and-mysql/
 

https://code.google.com/archive/p/php-apns/ 

I don’t know what would be required for sending notifications to Android mobile 
devices.

Best,
Bill P


> On Aug 16, 2017, at 11:27 AM, Richard Gaskin via use-livecode 
>  wrote:
> 
> Mike Kerner wrote:
> 
> > I disagree with Ben on the effort of rolling your own.  The first one
> > is probably some work, until you understand how push works, but after
> > you understand, it is pretty easy.
> 
> I don't mind learning new things, and I often prefer the control I get with 
> my own private systems.
> 
> What resources would you recommend for learning more about setting up a 
> notification server?
> 
> -- 
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> 
> ambassa...@fourthworld.comhttp://www.FourthWorld.com
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: sms,MMS, and Push Notificstions

[Mike Kerner via use-livecode]

I've been threatening to build/working on an LC push server library, but
it's on the back burner, right now, and probably will be until the end of
the year, at the earliest.
• First, go to quality.livecode.com, and add yourself to the cc list for
bug 10901 and 18692.  Those are for various improvements in push support
that will allow us to do things like silent push (push data to your app
without your app having to do it while it is running, wasting the user's
time).
• The piece that leaves the most to the imagination is handling the id
reporting from the devices.  On iOS, the only way to pull an app's push id
on a device is inside of the app.  So your app has to report its id to your
server, somehow.  "Somehow" can be a file drop (e.g. dropbox, since we talk
about that service a lot), a special port or URL, a web db query, etc.
• Your app checks to see if it has already reported its push id.  If it has
not, it reports it (however, there isn't any harm in reporting it each time
it launches).
• Perhaps your server implements a mechanism to notify your app that the
push id was received (e.g. by sending a push notification back), so that
the app does not notify the server, again, for this push id
• If your app notices that its push id has changed, it reports the old id
and the new id (or if you have some other way of keeping track of a
particular install on a particular device, you could report that with the
new id, instead).
• Check, periodically, to see if the push server is reporting that some id
or another is no longer active and should be taken out of service (I have
never received such a report, but you are supposed to do this, anyway).

On Wed, Aug 16, 2017 at 2:49 PM, William Prothero via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Mike:
> Me too on Richard’s request. I think the livecode lesson is a good start,
> but yes, setting up the server is another issue entirely. Since you’ve been
> through this process, it would be very useful to hear which learning
> resources you found most useful.
>
> Here are a couple of promising links I found by Googling around.
>
> This youtube video looks quite promising. It shows how to set up a server
> and the push notifications are sent using a cron job. I would bet the php
> code could be easily modified to sent the notification from a command on an
> app or mobile device.
> https://youtu.be/x4swrHvBqEw 
> More similar:
> https://webresourcesdepot.com/easy-apns-apple-push-
> notifications-with-php-and-mysql/  com/easy-apns-apple-push-notifications-with-php-and-mysql/>
> https://code.google.com/archive/p/php-apns/  archive/p/php-apns/>
> I don’t know what would be required for sending notifications to Android
> mobile devices.
>
> Best,
> Bill P
>
>
> > On Aug 16, 2017, at 11:27 AM, Richard Gaskin via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Mike Kerner wrote:
> >
> > > I disagree with Ben on the effort of rolling your own.  The first one
> > > is probably some work, until you understand how push works, but after
> > > you understand, it is pretty easy.
> >
> > I don't mind learning new things, and I often prefer the control I get
> with my own private systems.
> >
> > What resources would you recommend for learning more about setting up a
> notification server?
> >
> > --
> > Richard Gaskin
> > Fourth World Systems
> > Software Design and Development for the Desktop, Mobile, and the Web
> > 
> > ambassa...@fourthworld.comhttp://www.FourthWorld.com
> >
> > ___
> > use-livecode mailing list
> > use-livecode@lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode