The fundamental questions are always the hardest :-).
Let me try to see if the SOFEA definition is rigorous enough to answer this, since I'm most familiar with that.
Well, in the SOFEA world, we don't rule out a server component (the download server) serving up templates on demand as long as the client application is the one filling up the template with data. The restriction on the server side is against "Presentation Flow" and against mediating service requests. So any merging of data (from a service invocation) with templates should only be done on the client side. If the download server merges data with templates, then it means it is acting as an intermediary between the client and the business logic, which is forbidden.
I don't know if this makes things any clearer.
We could also define the View by elimination, I suppose, again in the context of SOFEA.
One part of the system deals with getting the application onto the client device so that it can run. This is the Application Download bit.
Another part of the system is the actual business logic which only has to do with non-visual data. Pass data in, get data out. This we called Data Interchange.
What's left in an application is Presentation Flow. The application is already running on the client and data is being transmitted to and from services. We have forbidden the use of server-side resources for any other purpose. So all remaining functions must now be done on the client. Whatever happens here is the View.
Does that explain it a little better?