NEO works with UNA API, but UI for modules needs to be adapted so initially not all modules will be compatible. The Starter Kits will come preconfigured for combined deployment UNA and NEO web app, with endpoints enabled for native apps as well.
Andrey, I guess what I'm wondering is if we start off with the current UNA core/Artificer template and configure our own "starter kit" instead of using a pre-configured one, will we have to do any extra work to get NEO compatibility if we continually update to current versions of the core/modules?