<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><h2 style="text-rendering: optimizelegibility; margin-top: 0px !important; margin-right: 0px; margin-bottom: 15px; margin-left: 0px; padding: 0px; line-height: 1.7; cursor: text; position: relative; font-size: 2em; border-bottom-width: 1px; border-bottom-style: solid; border-bottom-color: rgb(238, 238, 238); font-family: Helvetica, arial, freesans, clean, sans-serif; z-index: auto; ">Cordova Bridge for 'standard' AeroGear</h2><p style="margin: 15px 0px; font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 15px; line-height: 25px; ">We have talked about it before and it popped into my mind again when talking about the site re-structuring, that Cordova is basically a component as well. That combined with the idea that we have for the crypto plugin that it could be faster and more secure to make use of a native functions when they are available, made me think why not also bridge the 'standard' AeroGear features as well?</p><p style="margin: 15px 0px; font-family: Helvetica, arial, freesans, clean, sans-serif; font-size: 15px; line-height: 25px; ">Does that make sense? Or is this to much a nice to have will Javascript be 'good enough' in this case?</p><div><br></div></body></html>