5 ms·
Frameworks upon frameworks upon frameworks, running in a platform-dependent embedded mobile browser, wrapped together with AppGyver-specific API thunks for acce
by pavlov 12y ago
Frameworks upon frameworks upon frameworks, running in a platform-dependent embedded mobile browser, wrapped together with AppGyver-specific API thunks for accessing some native functionality in a non-standard way. There's tremendous impedance mismatch at every layer here.
I don't feel these deeply convoluted stacks are ever the right way to build a mobile app... Unless perhaps in the situation where you're already familiar with something like Angular and you know for sure that performance and look & feel won't be important criteria.
- kitsune_ 12y agoAmen, less is more. I think certain programming languages and ecosystems just naturally attract these huge, convoluted stacks, and I don't necessarily mean JavaScript, but UI programming in general. This shit has all been tried before. If you're familiar with .NET, let's just think back to the atrocity that was / is .NET Webforms + .NET AJAX. I think it's sad that certain people think that a frameworks like WPF or AngularJS are "great" or even "decent enough", it just shows you how abysmal the current state of UI programming really is.
- NicoJuicy 12y agoSo how would you do it any better? AngularJS and WPF are both great for their porpose. How much longer would it take if they had to write Apache Cordova/Ionic from the start? How much longer would you create a website without Bootstrap or jQuery?
- kitsune_ 12y agoRegarding the web, I'd start with functional paradigms and immutable data structures. I'd avoid monolithic stateful frameworks such as AngularJS. More in the vein of ReactJS, ClojureScript, Om, mori etc... http://www.slideshare.net/rangle_io/bertrand-k-functionalwebdevelopment http://www.slideshare.net/rangle_io/bertrand-k-functionalweb... https://www.youtube.com/watch?v=Elr_RNt2R5Q https://www.youtube.com/watch?v=Elr_RNt2R5Q
- yoka187 12y agoThe only browser you can run on iOS is the Mobile Safari, which is ok. Apple is slowly bringing in WKWebView which will be even better than Mobile Safari (there are still some issues apple has to crack though). And when it comes to Android devices, AppGyver works with Intel and crosswalk is used to bring unified experience on all devices. Crosswalk is fork of the newest chromium codebase. Check out https://crosswalk-project.org/ https://crosswalk-project.org/ for more information about this.
- woadwarrior01 12y agoAre you talking about UIWebView (rather than Mobile Safari)? And WKWebView is already available in iOS 8. The biggest thing that WKWebView brings to the table is JIT for JS which previously was available only to Mobile Safari and not to applications using UIWebkit. It does this by running an isolated process pool for rendering web content.
- disusered 12y agoThere's an issue with WKWebView and local file urls that's prevented Cordova contributors from moving forward with it http://shazronatadobe.wordpress.com/2014/09/18/cordova-ios-and-ios-8/ http://shazronatadobe.wordpress.com/2014/09/18/cordova-ios-a...
- hrktb 12y agoFeels like your are describing an enterprise app. That's also the same kind of situations where you have to freeze the hardware and software versions to keep it working, and in 5 years you still have to keep iOS8 devices running around, like it was done with IE6 in the old days.
- paulbennett 12y agoI agree with the second paragraph. It seems that we're constantly pushing to make developing mobile apps easier for people with a web front-end background, in doing so tying them into using a stack of frameworks that in my opinion is far enough removed from 'web' that it loses sight of the core advantage - that it is easier to learn and develop with than the 'native' alternatives. I wonder if by the time you get to this stage you wouldn't be better off investing the time in actually learning the native languages and toolsets provided with them. I am also concerned about how much you would be tied into doing things the, in this case, Supersonic way. The scaffolding for example looks interesting, but is it actually useful in a real-world application? I don't have experience with Supersonic, I do have experience with AngularJS + Cordova mobile apps (I built the front-end of the RuneScape Companion app) - and I think if I were faced with building a similar app again I would think very very carefully about investing time into learning a stack of frameworks such as this.
- colordrops 12y agoThis type product fits a specific niche. If you are a small team with a lot of web experience, no mobile experience, and only enough funds for one guy to work on your mobile app, then this might be a good choice. While there are some technologies that would need to be learned to build on this stack, it's meeting you half way as a web dev, so it will still be a lot faster than learning native dev from scratch. You will also save a lot of time by only coding for one platform instead of two. A stack like this though may not be the best approach to maintain as the user base and dev team size grows, but it will get you off the ground with limited resources and time.
- joeyspn 12y agoCouldn't have said it better...
- jbergens 12y agoIt's still early in the development of mobile stacks. It might be a huge risk to use a completely new framework built on another framework right now but in a few years it might have evolved to the standard way of doing things. If they get the tooling and own code to a stable state where everything just works it might save a lot of developer time. Or it might be safer to just go with Cordova or similar and use any UI and JS framework you like (that is stable enough).
- saurik 12y agoHave you ever actually watched an episode of MacGyver? I feel like if you have, this "AppGyver" project sounds like it has just about the right amount of duct tape. http://macgyver.wikia.com/wiki/List_of_problems_solved_by_MacGyver http://macgyver.wikia.com/wiki/List_of_problems_solved_by_Ma...
- coldtea 12y agoReminds me more of MacGruber: https://www.youtube.com/results?search_query=mccruber https://www.youtube.com/results?search_query=mccruber
- andybak 12y agoI am beginning to wish every HN story had two comments sections - one for meta comments such as this and one for comments more directly addressing the original post. Quite often I read the comments mainly for one or for the other. But it's distracting when you want to read comments commenting on THIS framework vs other frameworks to wade through a long initial sub-thread questioning frameworks entirely. :-) Same happens every time someone posts an ORM article, or a CMS article or anything on Angular.js whatsoever. Oh - and god forbid a Google product announcement might generate a debate on anything other than "Google will just close this down just like they did with Reader". I've got no objection to the parent's comments - but this type of comment always ends up at the top and dominates the more on-topic stuff further down.
- tzm 12y agoI empathize with your position, but I think your last sentence defines a very large market. If I look at it from a product lens, Supersonic is optimizing performance, UX and tooling within the hybrid space, which is valuable offer. From an engineering perspective, I would inspect the native API bindings and look for / test optimized rewrites of the Cordova runtime. I believe they are getting close to 3x gains over the stock Cordova runtime.
- thewarrior 12y agoI normally disagree with the excessive snark here but OP is right here. Things are getting ridiculously complicated.