Alternatives to jQuery Mobile logo

Alternatives to jQuery Mobile

Zepto, Bootstrap, AngularJS, jQuery UI, and Framework7 are the most popular alternatives and competitors to jQuery Mobile.
1.4K
293
+ 1
0

What is jQuery Mobile and what are its top alternatives?

jQuery Mobile is a HTML5-based user interface system designed to make responsive web sites and apps that are accessible on all smartphone, tablet and desktop devices.
jQuery Mobile is a tool in the Mobile UI Frameworks category of a tech stack.
jQuery Mobile is an open source tool with 9.8K GitHub stars and 2.5K GitHub forks. Here’s a link to jQuery Mobile's open source repository on GitHub

Top Alternatives to jQuery Mobile

  • Zepto

    Zepto

    While 100% jQuery coverage is not a design goal, the APIs provided match their jQuery counterparts. The goal is to have a ~5-10k modular library that downloads and executes fast, with a familiar and versatile API, so you can concentrate on getting stuff done. ...

  • Bootstrap

    Bootstrap

    Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...

  • AngularJS

    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • jQuery UI

    jQuery UI

    Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice. ...

  • Framework7

    Framework7

    It is a free and open source mobile HTML framework to develop hybrid mobile apps or web apps with iOS native look and feel. All you need to make it work is a simple HTML layout and attached framework's CSS and JS files. ...

  • Ionic

    Ionic

    Free and open source, Ionic offers a library of mobile and desktop-optimized HTML, CSS and JS components for building highly interactive apps. Use with Angular, React, Vue, or plain JavaScript. ...

  • Sencha Touch

    Sencha Touch

    Sencha Touch 2, a high-performance HTML5 mobile application framework, is the cornerstone of the Sencha HTML5 platform. Built for enabling world-class user experiences, Sencha Touch 2 is the only framework that enables developers to build fast and impressive apps that work on iOS, Android, BlackBerry, Kindle Fire, and more. ...

  • jQuery

    jQuery

    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. ...

jQuery Mobile alternatives & related posts

Zepto logo

Zepto

294
66
3
Minimalist JavaScript library for modern browsers, with a jQuery-compatible API
294
66
+ 1
3
PROS OF ZEPTO
  • 3
    Lightweight
CONS OF ZEPTO
    Be the first to leave a con

    related Zepto posts

    Bootstrap logo

    Bootstrap

    53K
    11.9K
    7.6K
    Simple and flexible HTML, CSS, and JS for popular UI components and interactions
    53K
    11.9K
    + 1
    7.6K
    PROS OF BOOTSTRAP
    • 1.6K
      Responsiveness
    • 1.2K
      UI components
    • 943
      Consistent
    • 778
      Great docs
    • 677
      Flexible
    • 466
      HTML, CSS, and JS framework
    • 411
      Open source
    • 375
      Widely used
    • 368
      Customizable
    • 241
      HTML framework
    • 76
      Popular
    • 76
      Easy setup
    • 75
      Mobile first
    • 56
      Great grid system
    • 50
      Great community
    • 38
      Future compatibility
    • 34
      Integration
    • 28
      Very powerful foundational front-end framework
    • 24
      Standard
    • 23
      Javascript plugins
    • 19
      Build faster prototypes
    • 18
      Preprocessors
    • 14
      Grids
    • 8
      Clean
    • 7
      Good for a person who hates CSS
    • 4
      Easy to setup and learn
    • 4
      Rapid development
    • 4
      Love it
    • 3
      Great and easy to use
    • 2
      Great and easy
    • 2
      Provide angular wrapper
    • 2
      Community
    • 2
      Powerful grid system, Rapid development, Customization
    • 2
      Popularity
    • 2
      Great customer support
    • 2
      Clean and quick frontend development
    • 2
      Easy to use
    • 2
      Great and easy to make a responsive website
    • 2
      Sprzedam opla
    • 1
      Material-ui
    • 1
      Geo
    • 1
      It's fast
    • 1
      Boostrap
    • 1
      Pre-Defined components
    • 1
      Not tied to jQuery
    • 1
      Responsive design
    • 1
      Design Agnostic
    • 1
      Recognizable
    • 1
      Intuitive
    • 1
      Love the classes?
    • 1
      Reactjs
    • 1
      Felxible, comfortable, user-friendly
    • 1
      The fame
    • 1
      Easy setup2
    • 1
      Painless front end development
    • 1
      So clean and simple
    • 1
      Numerous components
    • 0
      Frefsd
    CONS OF BOOTSTRAP
    • 25
      Javascript is tied to jquery
    • 16
      Every site uses the defaults
    • 15
      Grid system break points aren't ideal
    • 14
      Too much heavy decoration in default look
    • 8
      Verbose styles
    • 1
      Super heavy

    related Bootstrap posts

    Ganesa Vijayakumar
    Full Stack Coder | Module Lead · | 19 upvotes · 2.5M views

    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more
    Francisco Quintero
    Tech Lead at Dev As Pros · | 13 upvotes · 790K views

    For Etom, a side project. We wanted to test an idea for a future and bigger project.

    What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

    You kind of need a map to work as a proxy between the software and Google Maps API.

    We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

    Thanks to all the people behind Create React App it's easier to start any React application.

    We also chose a module called Reactstrap which is Bootstrap UI in React components.

    An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

    Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

    See more
    AngularJS logo

    AngularJS

    45.6K
    32.9K
    5.2K
    Superheroic JavaScript MVW Framework
    45.6K
    32.9K
    + 1
    5.2K
    PROS OF ANGULARJS
    • 887
      Quick to develop
    • 587
      Great mvc
    • 571
      Powerful
    • 521
      Restful
    • 503
      Backed by google
    • 348
      Two-way data binding
    • 343
      Javascript
    • 328
      Open source
    • 305
      Dependency injection
    • 197
      Readable
    • 75
      Fast
    • 64
      Directives
    • 63
      Great community
    • 56
      Free
    • 38
      Extend html vocabulary
    • 29
      Components
    • 26
      Easy to test
    • 24
      Easy to learn
    • 23
      Great documentation
    • 23
      Easy to templates
    • 21
      Easy to start
    • 17
      Light weight
    • 17
      Awesome
    • 14
      Javascript mvw framework
    • 14
      Angular 2.0
    • 13
      Great extensions
    • 13
      Efficient
    • 10
      Easy to prototype with
    • 8
      Coffeescript
    • 8
      High performance
    • 7
      Lots of community modules
    • 7
      Two-way binding
    • 7
      Mvc
    • 6
      Clean and keeps code readable
    • 6
      Easy to e2e
    • 5
      One of the best frameworks
    • 5
      Easy for small applications
    • 4
      Works great with jquery
    • 4
      Fast development
    • 2
      Be a developer, not a plumber.
    • 2
      Hierarchical Data Structure
    • 2
      I do not touch DOM
    • 2
      The two-way Data Binding is awesome
    • 2
      Dart
    • 2
      Typescript
    • 2
      Community
    • 2
      Declarative programming
    • 1
      Programming fun again
    • 1
      Acoperișul
    • 1
      The powerful of binding, routing and controlling routes
    • 1
      Fkin awesome
    • 1
      Opinionated in the right areas
    • 1
      Supports api , easy development
    • 1
      Common Place
    • 1
      Great
    • 1
      Very very useful and fast framework for development
    • 1
      Amazing community support
    • 1
      Readable code
    • 1
      Linear learning curve
    • 1
      Scopes
    • 0
      Httpș//Acoperișul 0757604335
    • 0
      Google.com
    • 0
      Bot Ionescu
    • 0
      Angular js
    • 0
      Js
    • 0
      Oautho loc
    • 0
      Shvzjn
    • 0
      Acoperișul 0757604335
    CONS OF ANGULARJS
    • 10
      Complex
    • 3
      Dependency injection
    • 2
      Learning Curve
    • 2
      Event Listener Overload
    • 1
      Hard to learn

    related AngularJS posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.1M views

    Our whole Node.js backend stack consists of the following tools:

    • Lerna as a tool for multi package and multi repository management
    • npm as package manager
    • NestJS as Node.js framework
    • TypeScript as programming language
    • ExpressJS as web server
    • Swagger UI for visualizing and interacting with the API’s resources
    • Postman as a tool for API development
    • TypeORM as object relational mapping layer
    • JSON Web Token for access token management

    The main reason we have chosen Node.js over PHP is related to the following artifacts:

    • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
    • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
    • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
    • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 20 upvotes · 816.3K views

    Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

    • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
    • Vue Styleguidist as our style guide and pool of developed Vue.js components
    • Vuetify as Material Component Framework (for fast app development)
    • TypeScript as programming language
    • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
    • ESLint, TSLint and Prettier for coding style and code analyzes
    • Jest as testing framework
    • Google Fonts and Font Awesome for typography and icon toolkit
    • NativeScript-Vue for mobile development

    The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

    • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
    • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
    • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
    • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
    • Large scaling. Vue.js can help to develop pretty large reusable templates.
    • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
    See more
    jQuery UI logo

    jQuery UI

    36.2K
    9.6K
    896
    Curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library
    36.2K
    9.6K
    + 1
    896
    PROS OF JQUERY UI
    • 213
      Ui components
    • 155
      Cross-browser
    • 121
      Easy
    • 100
      It's jquery
    • 81
      Open source
    • 57
      Widgets
    • 48
      Plugins
    • 46
      Popular
    • 39
      Datepicker
    • 23
      Great community
    • 7
      DOM Manipulation
    • 6
      Themes
    • 0
      Some good ui components
    CONS OF JQUERY UI
    • 1
      Does not contain charts or graphs

    related jQuery UI posts

    Ganesa Vijayakumar
    Full Stack Coder | Module Lead · | 19 upvotes · 2.5M views

    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more
    Khauth György
    CTO at SalesAutopilot Kft. · | 12 upvotes · 384.1K views

    I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

    Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

    On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

    On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

    See more
    Framework7 logo

    Framework7

    133
    296
    171
    Full Featured HTML Framework For Building iOS Apps
    133
    296
    + 1
    171
    PROS OF FRAMEWORK7
    • 21
      Free and open source
    • 20
      Well designed
    • 17
      Material design
    • 15
      Lots of ready-to-use ui elements, easy to customize
    • 12
      Best performance
    • 11
      Amazing documentation
    • 9
      Nice look and best performance
    • 9
      Performance and great features.
    • 9
      Rtl support
    • 7
      Free
    • 6
      Basic Web App Development Technique
    • 6
      Nice sample provided
    • 6
      Easy To Learn
    • 5
      It's feels light to use
    • 5
      Quick inital time
    • 5
      Easy to use , transit from vanilla JS
    • 5
      Doesn't require learning a JS framework
    • 2
      Easy to integrate
    • 1
      D
    CONS OF FRAMEWORK7
    • 1
      Not suitable for high performance in PWA. desktop apps

    related Framework7 posts

    Jonathan Pugh
    Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 1.6M views

    I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

    For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

    Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

    I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

    I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

    I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

    I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

    For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

    For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

    For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

    I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

    So that's my latest mobile stack. What tools do you use? Have you tried these ones?

    See more
    Michell Jose Gutierrez Rincon
    web & mobile developer at Freelancer · | 1 upvote · 70.5K views
    Shared insights
    on
    Framework7Framework7Apache CordovaApache Cordova

    Working with Framework7, Apache Cordova

    See more
    Ionic logo

    Ionic

    7.2K
    6.6K
    1.7K
    A beautiful front-end framework for developing cross-platform apps with web technologies like Angular and React.
    7.2K
    6.6K
    + 1
    1.7K
    PROS OF IONIC
    • 246
      Allows for rapid prototyping
    • 226
      Hybrid mobile
    • 208
      It's angularjs
    • 184
      Free
    • 178
      It's javascript, html, and css
    • 108
      Ui and theming
    • 76
      Great designs
    • 74
      Mv* pattern
    • 70
      Reuse frontend devs on mobile
    • 64
      Extensibility
    • 31
      Great community
    • 28
      Open source
    • 22
      Responsive design
    • 20
      Good cli
    • 13
      Angularjs-based
    • 13
      Beautifully designed
    • 13
      So easy to use
    • 12
      Widgets
    • 11
      Allows for rapid prototyping, hybrid mobile
    • 11
      Typescript
    • 10
      Quick prototyping, amazing community
    • 10
      Easy setup
    • 8
      Angular2 support
    • 7
      Fast, easy, free
    • 7
      Because of the productivity and easy for development
    • 7
      So much thought behind what developers actually need
    • 7
      Base on angular
    • 6
      Super fast, their dev team is amazingly passionate
    • 6
      Easy to use
    • 6
      It's Angular
    • 4
      UI is awesome
    • 4
      Hot deploy
    • 3
      Material design support using theme
    • 3
      Amazing support
    • 3
      It's the future
    • 3
      Angular
    • 3
      Allow for rapid prototyping
    • 3
      Easy setup, development and testing
    • 3
      Ionic creator
    • 2
      User Friendly
    • 2
      It's angular js
    • 2
      Complete package
    • 2
      Simple & Fast
    • 2
      Fastest growing mobile app framework
    • 2
      Best Support and Community
    • 2
      Material Design By Default
    • 2
      Cross platform
    • 2
      Documentation
    • 2
      Because I can use my existing web devloper skills
    • 2
      Removes 300ms delay in mobile browsers
    • 1
      1
    • 1
      Native access
    • 1
      Typescript support
    • 1
      Ionic conect codeigniter
    • 1
      Fast Prototyping
    • 1
      All Trending Stack
    CONS OF IONIC
    • 20
      Not suitable for high performance or UI intensive apps
    • 15
      Not meant for game development
    • 2
      Not a native app

    related Ionic posts

    Saber Hosney
    Senior software engineer at Shortcut · | 7 upvotes · 67.9K views

    Greetings!

    I have been searching lately for frameworks to build mobile apps.

    We are trying to make something like a quiz app as a way for customers to contact us. I considered Ionic and React Native because we use JavaScript most of the time in websites, e.g., Vue.js/Nuxt.js. But Flutter seems a decent choice as well, especially since you can use Android/iOS-like components. We are looking for something that works in the long term, something that's time and cost-effective, especially when paired with backend services like Firebase or a GraphQL server. I would like to know your opinions and recommendations. Thank you!

    See more
    Melanie Verstraete
    Shared insights
    on
    IonicIonicFlutterFlutter

    Hi community, I am looking into how I should build my tech stack for a business/analytics platform. I am not very familiar with frontend development; when looking into cross-platform frameworks, I found a lot of options. What is the best cross-platform frontend framework to go with? I found Flutter interesting, but Ionic also looks promising? Thank you for the advice!

    See more
    Sencha Touch logo

    Sencha Touch

    75
    83
    28
    The leading mobile web app framework based on HTML5 for amazing mobile apps.
    75
    83
    + 1
    28
    PROS OF SENCHA TOUCH
    • 8
      Structured code
    • 5
      Mvc
    • 5
      PhoneGap intergation
    • 3
      Customised Component
    • 2
      Rich Charting Components
    • 2
      Mobile oriented theme
    • 2
      Easy Data Binding
    • 1
      Open source
    CONS OF SENCHA TOUCH
      Be the first to leave a con

      related Sencha Touch posts

      jQuery logo

      jQuery

      168.8K
      50.1K
      6.5K
      The Write Less, Do More, JavaScript Library.
      168.8K
      50.1K
      + 1
      6.5K
      PROS OF JQUERY
      • 1.3K
        Cross-browser
      • 957
        Dom manipulation
      • 805
        Power
      • 660
        Open source
      • 610
        Plugins
      • 457
        Easy
      • 395
        Popular
      • 350
        Feature-rich
      • 281
        Html5
      • 227
        Light weight
      • 91
        Simple
      • 84
        Great community
      • 79
        CSS3 Compliant
      • 69
        Mobile friendly
      • 67
        Fast
      • 43
        Intuitive
      • 42
        Swiss Army knife for webdev
      • 35
        Huge Community
      • 10
        Easy to learn
      • 3
        Clean code
      • 2
        Just awesome
      • 2
        Powerful
      • 2
        Nice
      • 2
        Because of Ajax request :)
      • 1
        Easy Setup
      • 1
        Open Source, Simple, Easy Setup
      • 1
        It Just Works
      • 1
        Improves productivity
      • 1
        Industry acceptance
      • 1
        Allows great manipulation of HTML and CSS
      • 1
        Used everywhere
      • 1
        Widely Used
      • 0
        Javascript
      CONS OF JQUERY
      • 5
        Large size
      • 5
        Encourages DOM as primary data source
      • 4
        Sometimes inconsistent API
      • 2
        Live events is overly complex feature

      related jQuery posts

      Kir Shatrov
      Engineering Lead at Shopify · | 20 upvotes · 566.1K views

      The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

      Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

      #FrameworksFullStack #Languages

      See more
      Ganesa Vijayakumar
      Full Stack Coder | Module Lead · | 19 upvotes · 2.5M views

      I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

      I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

      As per my work experience and knowledge, I have chosen the followings stacks to this mission.

      UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

      Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

      Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

      Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

      Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

      Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

      Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

      Happy Coding! Suggestions are welcome! :)

      Thanks, Ganesa

      See more