Meeting minutes
Second Draft progress: https://
Changes between First draft and Second draft: https://
Definitions drafts - Diagram
https://
Part of this Pull Request: w3c/
Old version: https://
New diagram: https://
Software or User Agent: renamed to Software
"underlaying layer" renamed to Hardware
Native program / Cross-platform program renamed "program" to "app"
Title updated to reflect content, it's now "Layers and responsibilities in mobile applications"
Prefixed the layers with numbers, e.g. "1. User" instead of "User"
Added dotted square around native app / cross-platform app, together named "Application Software"
<Joe_Humbert> Looks good to me
Diagram label section, could be made bigger by moving them to the left edge - gives extra space on the right
In the detailed description, use uppercase for each word
Definitions drafts - Application software
https://
Now contains a table
Application software - do we need to define what platform widgets mean
React Native can render native platform widgets; but what about custom components (or native apps with custom components)
Potentially second column can be removed to just provide examples of the types of apps and the frameworks that correspond
Semantics tree might also need definition
First sentence is OK
Second sentence: introduce the different ways that application software is built, point to table 1 with examples
Success Criterion 2.5.7 Dragging Movements
github.com/w3c/matf/pull/295
The concerns about "underlying layer terminology" should now be resolved because the diagram no longer uses it, so underlaying now refers to one layer below and not some other definition
Success Criterion 2.5.8 Target Size (Minimum)
https://
We need to decide which language to use in the note that links to the research, plus how to introduce our suggested target sizing
^ relates to note 3
Normative text content update: w3c/
<Joe_Humbert> w3c/