Re: ISSUE-237 (Define Mobile Web Applications): What is the definition of a "Mobile Web Application" for the purposes of BP2? [Mobile Web Applications Best Practices]

My formulation is...

A Mobile Web application is an application designed specifically to
work well on mobile devices, as opposed to traditional desktop
computers, or is perhaps designed primarily for mobile devices. A
Mobile Web application is described using an HTML or XHTML variant,
and is delivered to a suitable user agent on a mobile device over
HTTP. Such an application commonly uses CSS, or employs ECMA Script to
manipulate a DOM to implement interactive behavior, or uses so-called
"AJAX" technologies -- XML over HTTP, the XMLHTTPRequest object -- to
access data.

1) I want to be specific about technologies we're talking about, since
I think this is what we are talking about. I do think it will be
exceedingly hard to write real-world best practices without some
anchoring in the real world. We can refine which technologies we want
to mention, and how specifically. Perhaps we can proceed by continuing
to write concrete best practices (see my earlier message) and find out
that way what we are talking about.

2) I don't think we need to say "browser". This is about the content
written for something browser-like, not the user agent itself.


On Thu, Feb 21, 2008 at 11:42 AM, Mobile Web Best Practices Working
Group Issue Tracker <sysbot+tracker@w3.org> wrote:
>
>  ISSUE-237 (Define Mobile Web Applications): What is the definition of a "Mobile Web Application" for the purposes of BP2? [Mobile Web Applications Best Practices]
>
>  http://www.w3.org/2005/MWI/BPWG/Group/track/issues/
>
>  Raised by: Daniel Appelquist
>  On product: Mobile Web Applications Best Practices
>
>  We have a number of different (but I would say converging) views on what constitutes a Mobile Web Application.  My view is that we are talking about applications for which the user interface element executes in the browser/web technologies context. I would specifically put device APIs out of scope. I would specifically put widgets out of scope. I would specifically put non-"web" technologies such as flash and silverlight out of scope. Jo has suggested we could use the criterion of whether or not the technology uses the underlying technology of the DOM to define "Web technologies."  As agreed on today's call, this is an important enough issue to pull out from the discussion on scope and give it its own issue.  I want to come back to this issue on next week's call and take a resolution on this point so we can get this out of the way before the next F2f.
>
>  Discuss!
>
>  Dan
>
>
>
>
>

Received on Thursday, 21 February 2008 17:10:56 UTC