i was looking into it on their site and that was my take on it. hopefully i am wrong through and someone will correct me here

+Avinash Ananth Narayan R - thanks, we've gone full #AndroidNougat now :)

The blog post contains the following "Note: SSL/crypto is a special case, applications must NOT use platform libcrypto and libssl libraries directly, even on older platforms. All applications should use GMS Security Provider to ensure they are protected from known vulnerabilities."

So the takeaway from this is:

1. You are free to compile your own crypto or whatever libraries you want. But as has always been the case, you should never link your app against platform libraries that the NDK does not provide headers for, since they could change on you, like when there was a change from OpenSSL to BoringSSL.

2. If you don't want to maintain your own updates for crypto, but still be secure as possible, you should take advantage of GMS Security Provider to do this for you. However, this is not required, and you can always do your own SSL build if you want.

3. If you use a standard NDK build process, use the standard headers provided, and build your own required 3rd party libraries, then there will be no problem. If you are doing hacks and linking against symbols that are not exposed by the NDK, then the blog post explains what you need to fix to make your app work properly. While these hacks may have worked in the past, they rely on undefined behavior and hence the reason why we put this blog post together to help explain what is coming up in the future.

+***** 

+Ian Lake "the expectation is that developers handle split-screen and freeform exactly the same" -- users may disagree with you.

"If you have work that is a logical continuation of your task, you should continue to have that as part of your task (and hence, window)" -- again, users may disagree with you. Freeform multi-window does not have to exactly match the WIMP model that Windows and macOS users are used to, but the closer it gets, the fewer support issues developers will face.

"Do you have specific design configurations (aspect ratios, etc) that you don't see covered through testing split-screen multi-window?" -- everything needs to be re-tested on freeform multi-window. We won't know if there are design configurations that are an issue until we actually see how things work. That's why we test things. This isn't a question of known unknowns; it's a question of unknown unknowns.

Outside of a few sentences in documentation and random Medium posts, we have zero official information about freeform multi-window. The fact that we lack information is typical. And, we'll hack solutions around that lack of information as best we can, as we do with everything else. And I'm not surprised by the lack of freeform multi-window mode on Google devices. However, one would think that it would be in Google's interest for there to be some official testing solution for freeform multi-window before major manufacturers start shipping freeform multi-window devices.

Is that free?

A bunch of singles have downloaded this app, LoL.

I love the app!

Thanks +Ian Lake​. Any plans though? I think since the new features of android wear are announced that can happen. It would be really beneficial for watchfaces. 

Congrats +Katherine Kuan​, I learned a lot from you and your colleagues, so much. Thankssss

Interesting:)