Lets put it this way. I’ll talk about my specific case while I guess it’s the same with many more devs.
That happens using Cordova. And it’s great, but it comes with many limitations:
- Native performance
- Native page transitions
- Animations in general
- App fluidity
I tried also “Famous” and other js frameworks optimized for mobile use. Complexity rises just to get native-looking apps.
Too much effort and moving parts to just get decent performances.
Moreover framework like Meteor are all-in solution and I find myself having a different repository for the mobile version of my app. It just makes more sense and it’s easier to develop and maintain. So I was looking for mobile only solutions.
Native apps without the need to learn different languages for IOS and Android. A dream come true.
I thought that FuseTools would break into my next app project until I understood that only fetch() “works” at this time. I was about to recommend Fuse to everyone I know, but I simply had to stop.
That’s not where everything is heading. Real-time interactions, shared status among servers, multiple clients querying the database.
And every trending framework I know uses websockets (both ws and wss) for that. What I’m trying to say it’s that I know that websocket support is on your roadmap. I’m strongly suggesting you should put it on the top of your list.
IMHO websocket integration may boost Fuse adoption among devs. For example I would promote it in a couple of slack channels and forums.
You may appeal to communities like Meteor.com, Horizon.io, Deepstream.io, Hood.ie, Kuzzle.io
These are very active communities with a lot of open-minded people that I’m sure would much appreciate what Fuse (with websocket support) can offer.
The first time that websocket has been mentioned on this forum was 8 months ago…
Fuse is great, make it even greater.
That’s it. I rest my case