MCP Android Plugin Demo

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

MCP Android Plugin Demo

supittma
Administrator
TL;DR; here's the link : https://www.youtube.com/watch?v=8_yGFnYtIoQ

So the next two sprints the Client SDK team is working on MCP integration for Android in an attempt to replicate Aiden's demo from last week.  Right now we have build an Android app that parses a local mcp-config file and loads the configuration from the mcp server.  This configuration will be used to configure the sync and keycloak SDKs on the client.

One of the features we've put into our PoC is a Android build plugin that handles the parsing of the mcp-config file at build time instead of at run time.  This means that if the file is not present, is misconfigured, etc this error will be caught much sooner than if you have to load it onto an Android device.  Additionally it let's us have tighter integration with the Android build ecosystem as shown in the demo.

Summers

_______________________________________________
feedhenry-dev mailing list
[hidden email]
https://www.redhat.com/mailman/listinfo/feedhenry-dev
Reply | Threaded
Open this post in threaded view
|

Re: MCP Android Plugin Demo

David Martin
Hey Summers,

Nice video.
I like the idea of doing the config validation at build time.
I think its important that an App can launch to some usable state, even if offline (for the first or subsequent launches).

I'd like to know your thoughts on if there's value in having the config endpoint in the mcp server?
Why even bother with calling the endpoint if you could just take the config from that response and use that in your App?
(e.g. show the full config for all services in the MCP UI)

On 3 October 2017 at 14:20, Summers Pittman <[hidden email]> wrote:
TL;DR; here's the link : https://www.youtube.com/watch?v=8_yGFnYtIoQ

So the next two sprints the Client SDK team is working on MCP integration for Android in an attempt to replicate Aiden's demo from last week.  Right now we have build an Android app that parses a local mcp-config file and loads the configuration from the mcp server.  This configuration will be used to configure the sync and keycloak SDKs on the client.

One of the features we've put into our PoC is a Android build plugin that handles the parsing of the mcp-config file at build time instead of at run time.  This means that if the file is not present, is misconfigured, etc this error will be caught much sooner than if you have to load it onto an Android device.  Additionally it let's us have tighter integration with the Android build ecosystem as shown in the demo.

Summers

_______________________________________________
feedhenry-dev mailing list
[hidden email]
https://www.redhat.com/mailman/listinfo/feedhenry-dev




--
David Martin
Red Hat Mobile
Twitter: @irldavem
IRC: @irldavem (feedhenry, mobile-internal)

_______________________________________________
feedhenry-dev mailing list
[hidden email]
https://www.redhat.com/mailman/listinfo/feedhenry-dev
Reply | Threaded
Open this post in threaded view
|

Re: MCP Android Plugin Demo

supittma
Administrator


On Tue, Oct 3, 2017 at 1:00 PM, David Martin <[hidden email]> wrote:
Hey Summers,

Nice video.
I like the idea of doing the config validation at build time.
I think its important that an App can launch to some usable state, even if offline (for the first or subsequent launches).

I'd like to know your thoughts on if there's value in having the config endpoint in the mcp server? 
Why even bother with calling the endpoint if you could just take the config from that response and use that in your App? 
(e.g. show the full config for all services in the MCP UI)


Well there is value and I think we need A/B or Blue/Green style features to be competitive with other options, and having the download config pattern is one way to implement it.  We also have to support many options on many platforms and it is a least common denominator implementation even if there are technical limitations we get to overcome.  (Firebase sells a similar service called remote config). For some use cases this could be a core feature; configuration dashboard apps come to mind. From a support POV there are also options for enabling things like remote debugging, logging, etc. In development situations this will let us cut down on the turnaround time for testing service integrations which is beneficial during a app's early days. Eventually the dev scenario will need an easy way to "switch" to a static configuration for most apps.

If we have as a use case changing the server configuration at runtime then we need to think out the feature as a whole once we get past the MVP. 
 

On 3 October 2017 at 14:20, Summers Pittman <[hidden email]> wrote:
TL;DR; here's the link : https://www.youtube.com/watch?v=8_yGFnYtIoQ

So the next two sprints the Client SDK team is working on MCP integration for Android in an attempt to replicate Aiden's demo from last week.  Right now we have build an Android app that parses a local mcp-config file and loads the configuration from the mcp server.  This configuration will be used to configure the sync and keycloak SDKs on the client.

One of the features we've put into our PoC is a Android build plugin that handles the parsing of the mcp-config file at build time instead of at run time.  This means that if the file is not present, is misconfigured, etc this error will be caught much sooner than if you have to load it onto an Android device.  Additionally it let's us have tighter integration with the Android build ecosystem as shown in the demo.

Summers

_______________________________________________
feedhenry-dev mailing list
[hidden email]
https://www.redhat.com/mailman/listinfo/feedhenry-dev




--
David Martin
Red Hat Mobile
Twitter: @irldavem
IRC: @irldavem (feedhenry, mobile-internal)


_______________________________________________
feedhenry-dev mailing list
[hidden email]
https://www.redhat.com/mailman/listinfo/feedhenry-dev