> On Jul 27, 2017, at 10:48 AM, Matt Maier via use-livecode
> wrote:
> High market penetration of smartphones doesn't mean anyone actually has any
> idea how to use their smartphone. Most people are at about the
> Fischer-Price My First Shapes and Colors level. Except that they've aged
> out of
Word. I barely have any experience and I've already run into multiple
users/customers who think that "add to homescreen" is impossible hacker
magic.
High market penetration of smartphones doesn't mean anyone actually has any
idea how to use their smartphone. Most people are at about the
Fischer-Pr
Which point illustrates something I'm sure seasoned developers have known for a
long time: There is no way to write an app so that it will satisfy everyone,
especially these days with all the ways to deliver an app!
To illustrate, I had a gal here in the office lose some documents, because I
h
hh wrote:
>> RG wrote:
>> - What are the use-cases where a native app is a better choice than
>> a web app?
>> - What are the perceived benefits of web apps and native apps?
>> The first question is about actual capabilities, and the second
>> is about the psychological drivers of clients and c
Add to list as necessary. I've already pulled in a few items from other posts.
We can come up with a referendum/consensus on the topic.
Traditional Apps:
UP SIDE
Better performance
No dependent on an internet connection (if server is not installed locally)
Many people still prefer to own product
On Wed, Jul 26, 2017 at 5:27 PM, Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> hh wrote:
> >> RG wrote:
> >> My bigger question here is what needs to be delivered specifically
> >> in a web browser window vs a native app, and why?
> >
> > This questions browsers ("the w
