Page Comparison

...

1. Create a repository to hold the shared AGL gRPC API definitions so that server and client implementations can source them from a common location.  Some investigation will be required with respect to the most straightforward way of integrating this with the server and client implementations already in hand (e.g. integration with Meson) -  Repo name agl-grpc-protos. Scott getting a better handle on using proto files so it should be ready Not ready for Quillback. 
2. Finish converting the HTML5 demo homescreen and launcher to using the applaunchd gRPC API and removing the D-Bus API from the applaunchd codebase - completed for Pike
3. Finish investigation into a minimal set of advanced systemd sandbox features to turn on by default in the application templates - completed for Pike. Documentation needs to be addressed. 
4. Update the Flutter and HTML5 demo homescreen applications to use the latest agl-shell v3 features with respect to application start up and surface activation, matching the Qt demo homescreen features.  On the Flutter side, this may involve work in the Flutter embedder. -  Pike completed with agl-shell v4 for Web and Flutter. 
5. Investigate converting at least some of the demo homescreen applications to use the new agl-compositor gRPC API instead of the agl-shell wayland protocol. -completed for Quillback for Flutter and Qt. Need to check with Roger about Web Apps, Web apps,  and Qt.  
6. Define a gRPC version of the legacy application framework's agl-server-audiomixer API, extend the new agl-server-audiomixer daemon to implement it, and update the Qt demo mixer application to use it  - Not started. Probably will get completed for Quillback.  Decided not to use this approach. Eliminated per role volume controls and switched to using VSS. In the new flutter app, the mixer was replaced with more basic audio controls (bass, treble, fader, balance)
7. Investigate the effort required to define and implement gRPC APIs for the previous agl-service-bluetooth and agl-service-network bindings, with an eye to following through with implementing them if the effort seems reasonable.  The end goal of this would be to enable development of a Flutter demo settings application and potentially enhancing the HTML5 demo settings application - Not started
8. Investigate solutions for managing authorization tokens and potentially SSL certificates for VIS and/or gRPC.  One option that needs to be considered is integrating use of systemd-auth to pass things to daemons and applications. - Not started
9. Investigate enabling SELinux enforcing mode in the demo builds. - Not started

...