<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">following up from the team meeting, here is the current link to our Browser targets<div><br></div><div><a href="http://aerogear.org/docs/guides/AeroGearBrowserTargets/">http://aerogear.org/docs/guides/AeroGearBrowserTargets/</a></div><div><br></div><div>when this was created, i think it was very early on in the project.</div><div><br></div><div>the desktop browsers are probably ok at this point, ( i would like to remove IE9, though ).</div><div><br></div><div>Mobile Browsers i think can be revamped a little, Mobile Safari should probably be 6 and 7</div><div><br></div><div>we can probably add in Chrome for Android and FireFox for Android</div><div><br></div><div><br></div><div>WRT the other platforms, i think there is a JIRA to create a Matrix </div><div><div><br><div><div>On Jan 8, 2014, at 5:28 AM, Erik Jan de Wit <<a href="mailto:edewit@redhat.com">edewit@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><blockquote type="cite"><br>on this same topic, what % should we be looking at when thinking about dropping support for other platforms, like android and iOS<br></blockquote><br>Don’t think we should have a hard (written in stone) rule, but try and to be pragmatic about what we support.<br><br>Because if 10% would be the limit for browsers we could drop IE support all together ;)<br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br></blockquote></div><br></div></div></body></html>