> So it is about how the user perceives the application
The user here is the developer. Here's an explanation from the article:
> "some amount of server-side logic is still written by the application developer but unlike traditional architectures is run in stateless compute containers that are event-triggered, ephemeral (may only last for one invocation), and fully managed by a 3rd party ... One way to think of this is Functions as a Service."
Or do you mean that the user don't have to care on how to configure the application? Then "Zero-configuration" is a better name.
Or do you mean that the application hides that it use services on the net? Then it is even worse.