Does fuse let me export my project to a native Andriod Studio project?
If so, how?
I can build it to my phone as an APK but I do not see some standard Android project / folder to work with.
Thanks.
Hi! Right now there’s no simple way of integrating a Fuse-built UI into an existing Android Studio project. However, we have plans to fix this as well. 
Until then the easiest way to create things with Fuse is to build everything using UX and Javascript and then export complete apps.
So just to double check - I should not bother our developers about using Fuse generated-code to use with our existing project, but it’s on the road map?
Thanks.
That is correct.
We’ll try to not keep you waiting for too long, but in the meantime you can of course try out Fuse on its own. Anything you pick up on the front-end-creation side will of course continue to be applicable in the future.
Hi Remi. Any update or change on this topic? Does Fuse let me export to native / “normal” android views and XML’s etc.? I was really interested in getting the team to use Fuse, but it got shot down (9 mos ago)
N.
Hi again! There is no major change here, you still need to build the app in Fuse rather than exporting views for inclusion in other projects. This feature is definitely on our roadmap but it’s likely to be quite a while out yet as there’s a lot of other functionality with higher priority.
Hey Guys! I am new to Fuse, and the Only thing holding me back and the majority of people i know, from transitioning to Fuse and commit an entire team and a large multi million pound project 100% to Fuse is: we need to know that we will/can export it to Android Studio views and XML in future…as per your previous messages this seemed to have been close and on the roadmap a year ago…how is this going? I am really hoping for some kind of sign and guarantee here so that i can justify our full commitment…
We have been shipping a feature for this since Fuse 1.0.
Hi Erik
Thank you for your quick reply.
We are not looking, for imported Fuse Components into the Android Studio, but rather an actual generated conversion from Fuse Markups into Native Android XML. This is because, we need the actual Native android XML, in case, in future, we decide to move to Native for better access to Native Mobile specific mobile components, such as ‘Hovering’ icons on the Android Mobile main screen, outside of the app itself, etc etc…Bear in mind, that for very large projects, we really need the ability to revert back and forth to Native. Otherwise, to be frank, its quite risky, and we will always depend on you…… ;-))) Not that we would want to exclude Fuse, but rather use it, as part of our Product Roadmap, instead.
A good example of this, is my previous work at CBS Interactive, as their VP of Ops, where we had to develop extremely complex and mobile specific Apps…and a Fuse only app development, would never ever get approved by our CTO or Budget controller, should we not be able to fully revert back to Native or have a plan B…this sort of Flexibility is what is required for Very large dev teams, and ‘Serious’ heavy lifting projects and Budgets in Global Companies, such as CBS…my wish is that i can make this happen, so…sorry for long text…but once you get this done! The doors to large Multinationals will open very easily…:-))) just my take. I am YOUR BIGGEST FAN 
Cheers
Jorge
Thanks for the kind words and specific feedback!
However, at this point in time we have no plans for converting UX markup-based components to native Android XML.
While I haven’t looked into the details I suspect that might have resulted in a somewhat frustrating experience for the users considering all the things you can do in UX that are not possible to implement in Android XML (effectively forcing you into a strict subset of UX).
We instead try to give you access to all those neat native features through Fuse (for when you build your entire app in Fuse), and the ability to enrich apps made in Android Studio / Xcode by integrating custom components made in Fuse (e.g. what Erik linked to).