there 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
Fuse
41–50 of 100 posts
Re: Fuse
#42I really don't see the point. If you don't need cross platform the best choice is native so you can leverage all the platform goodies. If you do need cross platform and have the budget you will go with 2 native projects. If you don't have enough budget for 2 native apps you have a few options. Cordova is good enough for a lot of apps. Even Apple uses Webviews in its own apps. Also check the Missive mail client all bu…
TL;DR We're primarily about being able to create cool stuff in less time (cross-platform is just a side-effect of that). A lot of what we build comes down to creating good workflows for going from idea to the final product, and to find the right level of abstraction so that you can work very quickly (staying focused on the real job rather than boilerplate and glue code) without giving up control and being sandboxed.
Re: Fuse
#43Lot of examples that look very promising really help to get into the main stuff quickly.
Tough, after learning React (preact actually) ; I'm wondering what it could help achieve more than going trough Native React. The last one is already well implemented and is "structured" like react, merging up some learning curve.
as Pier25 said earlier tough, trouble is when you need to implement "fancier" things. At which point you could have gotten into real native anyway.
It saves some time, but the pricing plans are ridiculous.
If you want to build a tool people want to use you need to build up something they'll like first.
I doubt anyone could be using it since more established tools are already been accepted by the community.
I will never pay you for a Visual Studio. I like coding with VIM or Subl, and I look after tools that I can use with a idiot text editor.
Hope you grow up from this :)
Cheers
edit: misread plans
Re: Fuse
#44Looks like Electron on steroids. The landing page is nice but it's like putting lipstick on a pig - it's still a pig in the end. Also, I never understood why people hate native languages so much - why do you want to replace everything with Javascript? It's shit - it's a necessary evil in the browser but when the environment gives you something better (Swift, Java, etc) why not enjoy it?
Re: Fuse
#45How is this different to React Native?
Re: Fuse
#46Earlier quoted context omitted.
> When did we decide that developer time was more precious than user experience anyway? I think people really over exaggerate native UI experiences... maybe a native experience is 10 out of 10 good and a non-native experience is something like 7 out of 10 good but it's not as bad as 1 out of 10 good. I'm sure there's lots of occasions where users will be happy with a non-native app rather than not having one at all b…
Spotify would be vastly improved going native. That thing has ridiculous lag when loading the app, trying to play a song. I have an older iPhone, so it's much more noticeable, but then when you use the built-in music app and see how fast it is, it's inexcusable. I've started buying music again instead of using Spotify because of it. It's not just my ancient iPhone though - the Mac Spotify client regularly sticks for…
Works great for me. I could understand not liking it if it did that on my machine though.
Re: Fuse
#47You actually need to know some programming if you want to write applications in Swift, Java or .NET. That's why.
Re: Fuse
#48Earlier quoted context omitted.
Spotify would be vastly improved going native. That thing has ridiculous lag when loading the app, trying to play a song. I have an older iPhone, so it's much more noticeable, but then when you use the built-in music app and see how fast it is, it's inexcusable. I've started buying music again instead of using Spotify because of it. It's not just my ancient iPhone though - the Mac Spotify client regularly sticks for…
> the Mac Spotify client regularly sticks for at least 30 seconds on the Browse screen, or if I try to search for an item. Works great for me. I could understand not liking it if it did that on my machine though.
Helpful to know I might be an isolated case, though.