Why I moved away from Sencha to Phonejs?
But today I am going to talk about specifically one framework, that is Sencha Touch. I was trying to something that can developed once and deployed everywhere. Yes, it is kinda new trend in mobile development now a days.
And I do have working experience with JQuery Moblie, but still I choose Sencha, due to its performance and preference for architecture. I did same mistake which Rob Sullivan mentioned couple of days back.
@kunjee it’s always a balance of being able to push yourself but make sure you don’t go over a cliff from the push.— Rob Sullivan (@DataChomp) March 23, 2014
I practically pushed my self over the cliff. I am particularly having nothing against Sencha Touch. It is nothing but the overly awesome product. May be problem is on my side. I am not only doing mobile work. Mobile application is part of bigger idea or bigger application. So, there are many other things than running that very same thing on mobile.
Framework should help and if I can’t get it up and running in hours it is coming into my way of development.
That same thing happened with me. I have tried Sencha Touch, other than having lots of boiler plate code; Sencha command tool is also broken. That is also few months back there is no way to generate store using command. I never understand why?
I have also tried Sencha Architect. It is good for starting but after using for sometime, it started coming into my way. And I was spending more time in learning tool than solving the real problem. I personally don’t like this kinda tools.
May be I am not smart enough to use Sencha products.
I spend quite a amount of time learning Sencha, and same amount of time I was able complete application using more simpler Phonejs. It is little slow at start up but at least I am not slowing down my application to get out of development state.