I've had experience building MeteorJS based (Cordova under the hood) mobile apps and they are dreadful. Wood advise against it. However, MeteorJS is a great framework and our app, Linkwok is built using MeteorJS.
Yes definitely. Investors (Tech. Angels, VCs etc.) are all open to the idea of 'free' products as long as there is a monetisation/revenue model in play.
You don't need to charge users to make money. Data for e.g. is a great avenue for revenue.
Why do you think all those investors invested in the likes of Google & FB anyway?
I'd really like to know what this means in the context of MeteorJS - particularly how the HTTP Push feature will affect MeteorJS in the long run. Does it make MeteorJS redundant?
I'd really like to know what this means in the context of MeteorJS - particularly how the HTTP Push feature will affect MeteorJS in the long run. Does it make MeteorJS redundant?
As am I. Over the last few years I became an Apple fanboy but ever since Windows 8 and Windows Phone 7, Microsoft has been moving in the right direction (apart from the start menu thing ofcourse)
Too bad MS has such a bad rap.
I am really looking forward to Windows 10. Pity they aren't doing enough for the power user & workstation user though - all that touch readiness is of no use to me cause I still use a desktop I built myself.
Interesting approach! However, as stated on the website, doesn't that lack of a UI port make it a pretty half-baked approach.
I understand of course that the way UI is coded in iOS is very different from Android.
I can see this is a far better approach than Cordova & PhoneGap in that I can just port the logic across from my Android app. I have always hated the Cordova approach and found it nothing better than a glorified hack.
Even so, while this approach should save dev time considerably for startups like ours won't it also complicate the dev cycle in terms of writing device independent logic?
Another question. Is it a two way tool? Will it convert my Objective C code to Java?
Also, your GitHub README is incomplete. Would like to see some proper examples.
That's exciting. I have worked extensively with Scala during my Master's project. What I'd really like to know is what this means in the context of the current trend of JavaScript (both client and server-side).
I'm currently working exclusively on MeteorJS, Node.JS and Angular and fail to see the relevance other than porting Scala applications to the web and making Web App development easier for developers familiar with Scala. However, without the kind of structure and inherent capabilities that a MeteorJS or DerbyJS offers, what's the USP here?
As for the name - The idea was that it's a wok(cooking pan) for what you find on the web.
And the video - I agree entirely. Any app should be simple enough that when you get there you know what to do. Unfortunately either we need to find a new UI/UX and Interactions guy or more likely it's a process to get a completely intuitive UI and we're working towards that. I'm just glad we hadn't posted the last version on HN - I'll admit it was appalling! As one commentator on Twitter said - it's like Prezi for research so please give it another go. There's a feedback button in the app that you can use. Thanks.
Sorry to hear that! And we didn't mean to override the scroll. We just wanted to draw all the focus on what Linkwok is and get users to the app faster. In any case we have put in a temporary fix without the whole grid layout until we do an overhaul. Thanks for the feedback!
Thanks for the feedback guys. We put in a temporary fix without the whole grid nav. We thought it was pretty cool. But good UI is always an iterative process and we're working to improve this.