<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi,</p>
<p>I've been thinking about some simple debugging procedures, seems
like we'll be asking users to:</p>
<p>1. Reload config json for mobile app (cos something might have
changed on OpenShift side)</p>
<p>2. Check a <a moz-do-not-send="true" href="not%20there">Compatibility
Matrix</a> to make sure that your sdks and services all match up
<br>
</p>
<p>That second step seems to be a non-optimal user experience, could
we add compatibility information to config json?</p>
<p>This would mean the user would not have to leave their IDE to
check out a compatibility issue.</p>
<p>How might it work?</p>
<p>Each update to a service could include the following info:<br>
</p>
<p>* compatibleWith <br>
</p>
<p>* incompatibleWith</p>
<p>and as part of updating a service, include known compatibility,
for example with Keycloak Service v2.3.1 you might have</p>
<p>"androidSDKCompatibleWith":[ "2.x.x", "3.x.x" ],</p>
<p>"androidSDKIncompatibleWith":[ "2.0.x" ]</p>
<p>The user can then check the SDK version and take action as
required,<br>
</p>
<p>WDYT?</p>
<p>Paul<br>
</p>
<pre class="moz-signature" cols="72">--
Paul Wright
Mobile Docs (github: finp)</pre>
</body>
</html>