I'm sorry you had to waste all that time on SSL today!
Something you might not know, but could be playing into the issues you were seeing is the key strength of the SSL cert. If you use a key strength larger than 512 bits, then you will start to see large connection delays between third party clients like MobiLinc and the ISY. The larger the SSL key, the longer it takes the ISY to handshake with MobiLinc.
In our testing 2048 bit keys can take close to 30 seconds to handshake with the ISY. MobiLinc for iOS is able to handle this really long delay, but MobiLinc for Android is not able to for various technical reasons.
For those that are interested in replacing the SSL cert with the ISY, we only recommend 512 bit to keep the handshake delay at a reasonable time, OR, use our MobiLinc Connect service which uses industry standard encryption/authentication and achieve fast connection performance.
We support both our MobiLinc Connect service users and those that still want to connect via a direct IP. We have no plans on changing this support and will fully support HTTP/HTTPS connections via MobiLinc and the ISY.
If you change your key back to 512 bits, are able to connect via HTTPS on your Android browser, but are still unable to connect via MobiLinc, please email our support email at: firstname.lastname@example.org
and we'll keep digging in to see what's happening.
Also, to address your MobiLinc/Android comments, we just released a major overhaul to the MobiLinc/Android UI to bring it more in line with Android 4.x design patterns. The two apps aren't intended to look identical, rather, we want to craft our MobiLinc apps to fit on the platform they are operating. The means support for the very powerful Tasker 3rd party app on Android where iOS is unable to match in terms of open functionality.