Why choose this over native apps?
To help fusetools make money.
Fuse
61–70 of 100 posts
Re: Fuse
#62My understanding is that it is designed primarily to facilitate the interaction between designers and devs and shorten cycle times.
Bent from Fuse here — that's indeed our primary design goal. We believe designers shouldn't necessarily learn to code, and coders shouldn't be fluent in design, but getting each role to come close together and to give them a common language and similar semantics, as well as a platform that enables quick iterations, is important to us.
Our CEO (and primary engine coder) was interviewed by Forbes earlier this year, and in the interview he touches on A LOT of these points: https://www.forbes.com/sites/julianmitchell/2017/06/29/this-...
Quick quote:
"Our (former) jobs as programmers at ARM gave us a front-row view of all the capabilities of modern mobile devices, and it became apparent that most developers underutilized a lot of these devices. As a consequence, much of the raw power didn't benefit the end users who bought these pocket-sized supercomputers. Secondly, the way apps are developed hasn't changed much in the last 20-30 years. New tools and computer languages have come and gone, but the process remains largely the same, with developers and designers operating in separate worlds, using a different set of tools.
This is partly because collaboration across these boundaries requires a huge amount of additional work just to translate and re-implement the vision of stakeholders and designers into production code. In turn, this resulted in unsustainable processes of slow iterations for testing and validating ideas. Consequently, you end up with products and user experiences that are less thought-through or polished, even though you've spent an unacceptable amount of time, resources and risk to produce them.
These two takeaways lead us to realize that what was needed wasn’t another micro-optimization tool. We had to take a step back and consider the entire development process from through the lens of product owners and designers, as well as developers. Fuse is the byproduct of that process."
Re: Fuse
#63So it's like Xamarin with less performs??
Bent from Fuse here: I wouldn't say so. Xamarin strikes us as something meant for people who want to code C# and work within the .NET ecosystem, while Fuse takes a completely different approach (to both how you develop your apps, and what you spend your time on while doing it). The choice of JS for business logic was also made to enable more people to find an easier path into app development. Our UX Markup (that compiles to native C++ code) is one thing that makes Fuse differ quite a lot from many other frameworks.
Re: Fuse
#64This looks like Electron for mobile. If so; kill it with fire.
Re: Fuse
#65This looks like Electron for mobile. If so; kill it with fire.
It fills the same space as Electron, but does not function like Electron. The majority of code is written with UX, which is then compiled to Native components. It is also possible to have trivial FFI to native code with objc and Java. JavaScript is only used for _some_ business logic.
Re: Fuse
#66Die, JS, die!
There is very little JS in Fuse -- only some business logic. It's entirely possible to only have your business logic written in Uno, which compiles down to native code on each platform. All UI code is written in UX, which already does this.
Re: Fuse
#67Die, JS, die!
[deleted]
Re: Fuse
#68$125 / month bye
The free version is _free_. The only thing you would have to pay for is the "studio", aka the dev tools.
Re: Fuse
#69there was a team at my work evaluating Fuse, some very vocal fans, but they ended up going with React Native has anybody actually used Fuse for a real product? we could not find anyone to talk with about it and that was a deal breaker
There is a bunch of people on the community slack who are using Fuse to make things. Generally, any question you may have will be answered in there. The dev team sit in there too, so it's first hand help
@bent or whoever from fuse team ; THIS is a great thing. Having a active slack channel with people that work on and with the tool is was a great deal for me learning other stuff. I will join you guys here :D
Re: Fuse
#70Earlier quoted context omitted.
> Also, I never understood why people hate native languages so much - why do you want to replace everything with Javascript? Because people don't have the time, money or expertise to write multiple completely separate code bases for cross platform apps and having to keep these code bases in sync will dramatically slow down your ability to extend and adapt your product...?
Cross platform apps don't need to have separate codebases. Cross platform libraries and toolkits do exist.
Existing is not sufficient.
Convince us one of those tools is any good, because it doesn't seem like it, from the traction they've had so far.