Developer-Documentation-Overview.md

@@ -72,17 +72,22 @@ Librem5. (issue [1](https://source.puri.sm/guido.gunther/Apps_Issues/issues/1))
  * List some guidelines for writing apps.
  * Guidelines for development (like the existing Design page) (issue [19](https://source.puri.sm/Librem5/developer.puri.sm/issues/19))
 
-### Overviews
+### Overviews/Guides
+
+*(I believe Android calls these Developer Guides, if I remember correctly.)*
 
 #### Phone components
 
-This may be more of an architecture issue rather than a development issue, but it helps if developers know how the system behaves.
+Things like the dialler, contact, messaging, lock screen:
 
  * How they are used
+   * Some overlap with end user documentation
  * How they are configured
  * How they interact with applications
 
-#### Application interaction with the environment when using the phone
+*(This may be more of an architecture issue rather than a development issue, but it helps if developers know how the system behaves.)*
+
+#### Application interaction with the environment/components when using the phone
 
  *(Perhaps part of the previous section.)*
 
@@ -101,6 +106,7 @@ Also include software services that *might* be running:
  * Contacts
  * Messaging
  * Communication (cellular, wireless)
+ * Lock screen (part of the phone shell)
 
 These may also include system-level services from GNOME:
 
@@ -120,6 +126,8 @@ Interacting with remote services (if available):
 
 ### Sharing/Publishing
 
+ * Flatpak
+   * Any phone-specific configuration/permissions/features required?
  * Submitting apps to app store/getting apps published:
     *Once there's an app store in place, we will need to provide a how-to on submitting their apps.* (issue [19](https://source.puri.sm/Librem5/developer.puri.sm/issues/19))
  * Sideloading, testing?
@@ -128,9 +136,9 @@ Interacting with remote services (if available):
 
  * Catalogue pages linking into the API documentation.
  * Category pages with additional content.
-   *Not like overviews that would provide more context. These pages group together similar APIs and provide links to overviews as well as API references.*
+   * *Not like overviews that would provide more context. These pages group together similar APIs and provide links to overviews as well as API references.*
  * Generated APIs for components, from middleware up, and anything specific to the phone.
-   *For example, there may be a convenience API for accessing a hardware feature or it may be done via a standard API, but either case would have specific documentation.*
+   * *For example, there may be a convenience API for accessing a hardware feature or it may be done via a standard API, but either case would have specific documentation.*
 
 These contain links out to upstream documentation.