Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fuse

fusetools.com

Post reply on HN
Print view View original

91–100 of 100 posts

Re: Fuse

#91

Post by pier25 »

IshKebab wrote: post #81
pier25 wrote: post #11

I 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…

Even if you do have the budge for two native apps it may be that you would rather not spend all that money twice, or you would rather have one app with twice the features of two native apps. That said, all cross-platform solutions at the moment currently suck, except maybe Flutter, but that is still very alpha.

> it may be that you would rather not spend all that money twice

Maybe. My point is not about how you manage your budget, but how you make an app with the available budget for the app.

> or you would rather have one app with twice the features of two native apps

If you need those features then you can't really afford 2 native apps either.

Re: Fuse

#92

Post by pier25 »

gloom303 wrote: post #58
pawy wrote: post #43

I tried Fuse a while ago and even tough I didn't really got into it it was all very comfortable. Lot 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…

Bent from Fuse here again: thanks for the feedback — we definitely know of a lot of people who use both RN and Fuse for different projects. They both have advantages and disadvantages, depending on your team makeup, experience and what type of project you're working on. Your feedback around pricing is also duly noted.

I also think the pricing is unsustainable.

Even if you are making mobile apps all year round, what if tomorrow you don't want to use Fuse anymore? You'd need to keep on paying the subscription to fix bugs.

What if you are a freelancer who only makes mobile apps from time to time? Again you need to pay the whole enchilada to be able to fix little bugs from time to time.

A price per published app would make more sense IMO. Allow devs to use the complete experience for developing, make them pay when they need to compile and publish the app. If you are confident that your users will love your dev experience (which seems your stronger selling point) this would not feel like a trap.

Re: Fuse

#93

Post by voltagex_ »

gloom303 wrote: post #57
Rjevski wrote: post #6

Earlier quoted context omitted.

"iOS and Android from day one, with one shared codebase in UX Markup and JavaScript. You can also access all native features when needed by adding Objective-C, Swift or Java code directly to your project." (from their official site) I guess their actual compiler for "UX Markup" could be written in .NET but Javascript is definitely and unfortunately invited.

Bent from Fuse here — The UX Markup compiler is actually written in Uno, a lightweight C# dialect that compiles to native C++ for iOS and Android. JavaScript is just used for business logic and runs on a separate thread from the UI engine.

Will Uno ever be open sourced?

Re: Fuse

#94

Post by allover »

tjoff wrote: post #88
allover wrote: post #76

Earlier quoted context omitted.

> That Spotify, Whatsapp and Slack don't have native apps a disgrace beyond comprehension Pretty easy to comprehend why you wouldn't burn more developer resources than necessary actually. Try to set aside your own dev bias towards 'non-native' and consider what the average users of those apps think. They don't care the apps are non-native, they don't even know what that means.

> Pretty easy to comprehend why you wouldn't burn more developer resources than necessary actually. No, it is incredibly short sighted and in the long run Spotify in particular must have spent a ridiculous amount of effort ironing out bugs and issues (this often takes many many months) that are a consequence of unnecessary cross-platform efforts. The average user don't care about native and non-native. But they do ab…

Why is it short-sighted?

It's easier to transition from the (presumably) single code-base they have now to build specialised native apps later, if there's some expected pay-off, no?

But if they'd had separate code-bases all this time the maintenance effort to date would have been an order of magnitude higher. And consolidating to a single codebase from that would be a nightmare (should some new cross-platform toolkit mature).

> The average user don't care about native and non-native. But they do absolutely care about performance, look and feel.

And I've never heard anyone in my office (which has lots of non-devs) complain about Spotify's UI when they're changing the office music. Search for a song or playlist, play ... works fine as far as they're concerned.

Show me the evidence average users think there's a problem.

Re: Fuse

#95

Post by tripzilch »

allover wrote: post #76
tjoff wrote: post #40

Earlier quoted context omitted.

As a user, if good native is 10/10 non-native is at best 5/10. Usually though a native app isn't good so it's only 6-7/10. Non-native though are usually in the 2-4 range... That Spotify, Whatsapp and Slack don't have native apps is a disgrace beyond comprehension. Those are probably the easiest type of apps anyone can come up with.

> That Spotify, Whatsapp and Slack don't have native apps a disgrace beyond comprehension Pretty easy to comprehend why you wouldn't burn more developer resources than necessary actually. Try to set aside your own dev bias towards 'non-native' and consider what the average users of those apps think. They don't care the apps are non-native, they don't even know what that means.

> consider what the average users of those apps think. They don't care the apps are non-native, they don't even know what that means.

Just because the average user is unaware the shitty UX, performance or battery-draining is your app's fault, doesn't make it a good or professional choice. It means you can get away with it, because the user is unaware there was a choice, who's making it, and based on what criteria.

Re: Fuse

#96

Post by dang »

romanovcode wrote: post #47

> I never understood why people hate native languages so much You actually need to know some programming if you want to write applications in Swift, Java or .NET. That's why.

Please keep programming flamewars off HN. Other flamewars too.

We detached this subthread from https://news.ycombinator.com/item?id=14801059 and marked it off-topic.

Re: Fuse

#99

Post by andreashansen »

baalimago wrote: post #98
andreashansen wrote: post #86

Earlier quoted context omitted.

That's... not what Fuse solves.

then what does fuse solve?

You didn't read the link, did you? It's a cross-platform app development tool. The fact that it allows devs to use JavaScript is simply due to interpreters (afaik).
Post reply on HN