31–34 of 34 posts
Why would we abandon an aesthetic (that as of the L preview) that is two of the best and cleanest looking interfaces on the planet?
Earlier quoted context omitted.
The performance problems are not the fault of Cordova in the newest version which can be configured to use to the newest version of Chrome on android devices. Instead performance issues are the result of inefficiently manipulating DOM. Try famo.us with phonegap and you'll be able to overcome the performance issues you're seeing. disclaimer: I work for famo.us, but trust me here. do a proof of concept of something wit…
For a simple hybrid app (HTML5/JS/CSS packaged with Cordova) is there a reason to use famo.us instead of ionic?
I honestly haven't spent much time with Ionic and I have a conflict of interest, so take my position with a grain of salt, but AFAICT, thus far we (at famo.us) have spent more time building out the foundation (scene graph, perf optimizations, and physics engine integration) that allows a UI layer like Ratchet, Ionic or Material to be built on top. With that in mind, we haven't yet spent as much time on the UI layer, which is something we're doing now. Think: solid engine and architecture, but body work and trim in progress. Ionic (and Ratchet) on the other hand spent more time focusing on the UI layer, and is currently in the process of trying to modify the underpinnings to do the types of things famo.us is already capable of doing. Think: sexy looking car with an underpowered engine in the process of being upgraded.
However, again, my Ionic experience is pretty limited and a tad dated, so I urge you to do your own experimentation with both to see which best meets your needs right now. Personally, were I an outside developer, I would be choosing between famo.us and ReactJS instead of between famo.us and Ionic, since I'm personally "magic" averse and don't like tight coupling between the UI layer and the underlying layers that make that UI layer possible. The chrome on top is far less important to me (unless the goal is a quick prototype that I'm certain will be throwaway) than a solid modular architectural foundation that I comfortably know I won't be fighting as my app becomes larger and more complex. That being said, my broad generalizations here are based on my Ionic impressions from a few months ago. Things may have changed.
To further elaborate on what criteria I would use to choose between famo.us vs ReactJS, it comes down to this:
(1) Do I just need a (a) basic interface performance guarantee with discrete changes betweens application state and (b) greater backwards browser compatibility? Is my "app" going to be more traditional web app on desktop (vs Android and iOS like)? => ReactJS
(2) Do I need to make an app with not only a performance guarantee, but continuous transitions between application state (animations like those on capptivate.co), and will that application be largely consumed by people with relatively new mobile devices (smart phones or tablets, android or iOS)? => famo.us
Lastly, from what I've heard from fellow developers, famo.us and reactjs play pretty nicely together and we're going to be working on integration and tutorials between both, so it's possible that whichever one you start with today, you can add the other to get the best of both worlds. We're also starting work on an EmberJS and famo.us integration, so if you want a lot of the data and routing niceties of emberjs, but the interface niceties of famo.us, there should be tutorials and demo apps coming out in a few months.
Another option, which is very new, but gives you a lot of the reactjs benefits, but in a more modular packages that feel better to NodeJS developers is rayno's mercury project. It's still pretty new and documentation is lacking (which you can contribute to), but it takes the react ideas and breaks them down into smaller rearrangeable pieces.
Like every tool, you need to know the pros/cons and be able to apply them to your situation. Unless your goal is to make a super simple app that has 100% coverage across all mobile devices, Phonegap shouldn't be the tool you use. The market share of phonegap in hybrid apps is depressing to me. It's not hard to learn the Apple/Google sponsored way of doing things and then progressively decide when to bring in html/css…
Please point me to a place where I can understand how to do Objective C in a "not hard to learn" sort of way. There is way too much going on in XCode that a web developer wouldn't get or understand without having broad strokes glossing over the Interface, file structure, or behaviors included therein.
Earlier quoted context omitted.
Please point me to a place where I can understand how to do Objective C in a "not hard to learn" sort of way. There is way too much going on in XCode that a web developer wouldn't get or understand without having broad strokes glossing over the Interface, file structure, or behaviors included therein.
Over and over again I keep hearing people recommend the Big Nerd Ranch guide to Objective-C. I've briefly looked at it myself, but never got into iOS development so didn't pursue it seriously. With that in mind, I found it to be a very approachable resource, but that also comes with the caveat that any way you slice it, you're going to have to become familiar with computer science and programming language concepts an…
I've never wanted for better guides, books, and tutorials online for any of the languages I've gotten into. Specifically Golang and Java have both been much more approachable for me in recent months because I feel like I don't need a degree in rocket surgery just to open the IDE.
Maybe that's my problem. I'd rather not have to learn an IDE at the same time I'm having to learn a language. Now that I think about it, I also hated VS (but not Eclipse or the Jetbrains products).
Thanks, Doc ;) I think I just figured out my big problem!