Pros/Cons vs Onsen UI

Thanks for honest opinion. Personally I do not see myself as the target audience for a WYSIWYG editor – mainly because of the terrible code those types of editors tend to output (though I see clean code is touted as one of the features). But I understand your overall point in regards to surrounding services that can enhance a developers workflow. To that end, I believe: http://monaca.mobi/en/ is Onsen’s “answer” to Ionics surrounding services, but I may be wrong about that.

My 3 biggest concerns when comparing Onsen and Ionic are:

  1. http://components.onsenui.io/ - The ability to theme my app like this, so easily, is a HUGE draw for someone like me who is “challenged” in the way of design.
  2. This one post reference Onsen as having better list performance out of the box than Ionic: Ionic List Performance
  3. Ionic is in beta, while Onsen apparently is not. Though this is definitely not the biggest deal in the world for me.

My largest draws to Ionic when compared against Onsen are:

  1. Community. Onsen defers support to Stack Overflow
  2. Ionic’s Showcase. Proves to me there are production apps using Ionic in successful ways
  3. Ionic’s Activity. Onsen seems to have 1 primary programmer on GitHub, while it seems Ionic has 3-4.

I’m posting all this here just as a reference for others, or to be proven wrong on any of these points. Currently I am leaning in favor with Ionic because I feel that it’s likely only a matter of time before this team closes the gap on any of the concerns I listed above.

Thanks again

1 Like