I want to use a framework to develope in phonegap, i used jquery mobile for mobile web development but now i have performance problems with it. For example in android 2.3 the transitions efects are not working and in greaters versions of android work but they are not smooth (I try it on a galaxy s4).
Recently saw the appframework and their transitions are smooth so i want to use it without losing jquery Mobile power.
Any suggestion?
Related
I have been doing research to figure out the best way to create a mobile optimized website using Rails variants. I see that Framework 7 does this nicely, but I can't figure out if I can also do this with Ionic Framework? Can I use ionic components to create a mobile website that runs in a plain browser like Safari?
As Ionic works with AngularJS and according that the development process uses a simple http server on the folder /www, you can easily develop a mobile website with Ionic.
You will not have to use Cordova/Ionic plugins. But you'll can use HTML5 API to get geolocation or webcam access, etc.
But it is not because you can that you have to. Give it a try and tell us if you think it was a good idea.
Background: I've recently learned Ruby on Rails and have just learned to use JavaScript as well as JQuery. I've created some web apps using both.
Goal: To create a small e-commerce-like site using Rails backend but optimize for mobile. There will be a shopping cart but no built-in payment system.
I've seen these mobile app frameworks like ionic for mobile but am aware that ionic doesn't play nice with internet explorer for the desktop folks.
My idea is to use a mobile app framework like ionic or such for mobile and using a web framework like AngularJS for the desktop users for the same site. Or use a mobile app framework for mobile and no web framework for desktop?
I'm currently not advanced enough in my development skills to create adapters to use ionic or other mobile app frameworks to work friendly with desktop browsers. I'm looking for the more developer convenient route with style and with less configuration.
Please advise your recommendations and if you think that this setup can be done with minimal configuration with Rails as the backend.
Hybrid solutions will always be less good than native, in terms of performance, size and stability.
But Hybrid solutions are improving with time and ionic is a great solution, it avoids you to develop specific app for each platform.
To develop your hybrid app i warmly recommand you to use AngularJS, to me jQuery is not made to develop big application.
I'm new to Meteor and loving it but I'm having a hard time figuring out an ideal mobile framework to use for Mobile Web Apps, not native or hybrid strictly Mobile Web App (HTML5, CSS, Javascript) initially. Down the road I will create native versions with phonegap or native sdk.
Currently I've been using Bootstrap to make my apps responsive but ideally I'd like to use JQ Mobile for listviews, sliders, theming and other things.
I get the feeling that the main issue is the JQM Ajax Navigation and some DOM issues.
Any suggestions would be great, jQuery Mobile would be ideal but I get the feeling it doesn't play well with Meteor.
What is the difference of native packaging between Sencha touch2 and PhoneGap?
Many people use PhoneGap to natively package app based on Sencha touch, but I find that Sencha touch 2 has a new feature of native packaging.
So which type of native package is better in Performance, scalability, functionality, maturity, etc. ?
How do you choose?
PhoneGap is a middle-platform which is able to access some native APIs on many platforms and its interface language is Javascript. This means that PhoneGap is able to work with many cross-platform mobile web frameworks, such as: Sencha Touch, Titanium, jQuery Mobile, etc.
Sencha Touch 2 also provides a few native APIs (currently available on iOS, Android) through its SDK.
If you are not going to use any native APIs, then they don't have any major differences on performance and functionality as the only work done is just to wrap your Javascript code into a webview native component on corresponding device.
Lastly, the 2 main differences are:
PhoneGap provides much more APIs than Sencha Touch SDK.
PhoneGap supports 7 platforms, while Sencha Touch SDK only 2.
I had the same questions, I agree it's a real mess at first glance. Here is a very good article that "clears up confusion" quite well.
To quote the gist of the article:
Sencha Touch (and jQuery Mobile) are mobile web frameworks. You can use these technologies to create web-based, mobile apps. They don’t have access to any native API’s.
You can use Sencha Touch and jQuery Mobile inside both PhoneGap and Titanium. If you decide your html/js is cool as a native app too, you can use either PhoneGap or Titanium to wrap a browser around your app and put it in the app store or marketplace. This is where, I think, the confusion comes. Putting your Sencha Touch or jQuery Mobile apps in a native wrapper doesn’t make it a native app. It makes it appear as if it is a native app. You might get some extra functionality from PhoneGap or Titanium API’s, but it’s still not necessarily a ‘native’ app. It’s a web app running locally on the device. It’s a great way to use web technologies inside a native-like area.
The difference is that Sencha Touch allows you to build native iOS-Applications even on Windows, whereas PhoneGap 'only' bundles your HTML files into an XCode project, which further needs to be compiled on OSX for distribution/packaging.
PlayN looks like a pretty impressive way to develop Html5 games. I'm wondering if if there are any efforts to make the html/javascript output compatible with Phonegap with the end result being an iOS executable ?
PlayN works just fine with PhoneGap, and in Mobile Safari. Performance is not awesome because in PhoneGap, you cannot use JIT compiled JavaScript. Also, prior to iOS5, Canvas was not hardware accelerated. PlayN has a DOM+CSS backend for HTML5 that achieves decent performance on iOS4 and earlier, but it is being phased out in favor of a Canvas-only HTML5 backend. So that's added complexity if you want to target iOS via HTML5 + PhoneGap.
PlayN will eventually support iOS natively, and that will be a vastly preferable way to deploy to iOS because it will be more correct, higher performance, and integrate more easily with existing iOS services.