Alternatives to Zepto logo

Alternatives to Zepto

jQuery, jQuery Mobile, React, jQuery UI, and AngularJS are the most popular alternatives and competitors to Zepto.
279
46
+ 1
4

What is Zepto and what are its top alternatives?

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.
Zepto is a tool in the Javascript UI Libraries category of a tech stack.
Zepto is an open source tool with 14.7K GitHub stars and 4.1K GitHub forks. Here’s a link to Zepto's open source repository on GitHub

Zepto alternatives & related posts

jQuery logo

jQuery

124.2K
16.9K
6.6K
124.2K
16.9K
+ 1
6.6K
The Write Less, Do More, JavaScript Library.
jQuery logo
jQuery
VS
Zepto logo
Zepto

related jQuery posts

Kir Shatrov
Kir Shatrov
Production Engineer at Shopify · | 18 upvotes · 189.4K views
atShopifyShopify
jQuery
jQuery
JavaScript
JavaScript
React
React
TypeScript
TypeScript
Prototype
Prototype
#FrameworksFullStack
#Languages

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
Dan Robinson
Dan Robinson
at Heap, Inc. · | 18 upvotes · 151.3K views
atHeapHeap
jQuery
jQuery
Backbone.js
Backbone.js
Marionette
Marionette
TypeScript
TypeScript
React
React
MobX
MobX
#JavascriptUiLibraries
#Libraries
#JavascriptMvcFrameworks
#TemplatingLanguagesExtensions

The front end for Heap begun to grow unwieldy. The original jQuery pieces became difficult to maintain and scale, and a decision was made to introduce Backbone.js, Marionette, and TypeScript. Ultimately this ended up being a “detour” in the search for a scalable and maintainable front-end solution. The system did allow for developers to reuse components efficiently, but adding features was a difficult process, and it eventually became a bottleneck in advancing the product.

Today, the Heap product consists primarily of a customer-facing dashboard powered by React, MobX, and TypeScript on the front end. We wrote our migration to React and MobX in detail last year here.

#JavascriptUiLibraries #Libraries #JavascriptMvcFrameworks #TemplatingLanguagesExtensions

See more
jQuery Mobile logo

jQuery Mobile

1.3K
202
0
1.3K
202
+ 1
0
Touch-Optimized Web Framework for Smartphones & Tablets
    Be the first to leave a pro
    jQuery Mobile logo
    jQuery Mobile
    VS
    Zepto logo
    Zepto

    related jQuery Mobile posts

    Ganesa Vijayakumar
    Ganesa Vijayakumar
    Full Stack Coder | Module Lead · | 15 upvotes · 676.8K views
    Codacy
    Codacy
    SonarQube
    SonarQube
    React
    React
    React Router
    React Router
    React Native
    React Native
    JavaScript
    JavaScript
    jQuery
    jQuery
    jQuery UI
    jQuery UI
    jQuery Mobile
    jQuery Mobile
    Bootstrap
    Bootstrap
    Java
    Java
    Node.js
    Node.js
    MySQL
    MySQL
    Hibernate
    Hibernate
    Heroku
    Heroku
    Amazon S3
    Amazon S3
    Amazon RDS
    Amazon RDS
    Solr
    Solr
    Elasticsearch
    Elasticsearch
    Amazon Route 53
    Amazon Route 53
    Microsoft Azure
    Microsoft Azure
    Amazon EC2 Container Service
    Amazon EC2 Container Service
    Apache Maven
    Apache Maven
    Git
    Git
    Docker
    Docker

    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
    React logo

    React

    32.1K
    24K
    3.4K
    32.1K
    24K
    + 1
    3.4K
    A JavaScript library for building user interfaces
    React logo
    React
    VS
    Zepto logo
    Zepto

    related React posts

    Vaibhav Taunk
    Vaibhav Taunk
    Team Lead at Technovert · | 27 upvotes · 231.9K views
    .NET Core
    .NET Core
    Angular CLI
    Angular CLI
    React
    React
    MongoDB
    MongoDB
    Flutter
    Flutter
    React Native
    React Native
    Postman
    Postman
    Markdown
    Markdown
    Visual Studio Code
    Visual Studio Code

    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

    See more
    Dmitry Mukhin
    Dmitry Mukhin
    CTO at Uploadcare · | 22 upvotes · 369.6K views
    atUploadcareUploadcare
    Django
    Django
    Python
    Python
    React
    React
    Ember.js
    Ember.js
    Preact
    Preact
    PostCSS
    PostCSS

    Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

    Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

    For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

    However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

    All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

    See more
    jQuery UI logo

    jQuery UI

    28.5K
    3.9K
    894
    28.5K
    3.9K
    + 1
    894
    Curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library
    jQuery UI logo
    jQuery UI
    VS
    Zepto logo
    Zepto

    related jQuery UI posts

    Ganesa Vijayakumar
    Ganesa Vijayakumar
    Full Stack Coder | Module Lead · | 15 upvotes · 676.8K views
    Codacy
    Codacy
    SonarQube
    SonarQube
    React
    React
    React Router
    React Router
    React Native
    React Native
    JavaScript
    JavaScript
    jQuery
    jQuery
    jQuery UI
    jQuery UI
    jQuery Mobile
    jQuery Mobile
    Bootstrap
    Bootstrap
    Java
    Java
    Node.js
    Node.js
    MySQL
    MySQL
    Hibernate
    Hibernate
    Heroku
    Heroku
    Amazon S3
    Amazon S3
    Amazon RDS
    Amazon RDS
    Solr
    Solr
    Elasticsearch
    Elasticsearch
    Amazon Route 53
    Amazon Route 53
    Microsoft Azure
    Microsoft Azure
    Amazon EC2 Container Service
    Amazon EC2 Container Service
    Apache Maven
    Apache Maven
    Git
    Git
    Docker
    Docker

    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
    Khauth György
    CTO at SalesAutopilot Kft. · | 12 upvotes · 149.6K views
    atSalesAutopilot Kft.SalesAutopilot Kft.
    Amazon CloudWatch
    Amazon CloudWatch
    Amazon SNS
    Amazon SNS
    Amazon CloudFront
    Amazon CloudFront
    Amazon Route 53
    Amazon Route 53
    MySQL
    MySQL
    MongoDB
    MongoDB
    Redis
    Redis
    jQuery UI
    jQuery UI
    Vue.js
    Vue.js
    Vuetify
    Vuetify
    vuex
    vuex
    Docker
    Docker
    Jenkins
    Jenkins
    AWS CodePipeline
    AWS CodePipeline
    GitHub
    GitHub

    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
    AngularJS logo

    AngularJS

    20.7K
    13.2K
    5.2K
    20.7K
    13.2K
    + 1
    5.2K
    Superheroic JavaScript MVW Framework
    AngularJS logo
    AngularJS
    VS
    Zepto logo
    Zepto

    related AngularJS posts

    Jake Stein
    Jake Stein
    CEO at Stitch · | 15 upvotes · 123.7K views
    atStitchStitch
    AngularJS
    AngularJS
    React
    React
    CoffeeScript
    CoffeeScript
    JavaScript
    JavaScript
    ES6
    ES6

    Stitch’s frontend is used to configure data sources and destinations and monitor the status of each. Although we have been using AngularJS since its early days, we recently introduced React components into our front end, which many of our developers find easier to work with. We started using CoffeeScript when it was one of the few options for a more expressive alternative to vanilla JavaScript, but today we opt to instead write new code in ES6, which we feel is a more mature alternative.

    See more
    Arik Fraimovich
    Arik Fraimovich
    AngularJS
    AngularJS
    Angular 2
    Angular 2
    React
    React
    Vue.js
    Vue.js

    When Redash was created 5 years ago we chose AngularJS as our frontend framework, but as AngularJS was replaced by Angular 2 we had to make a new choice. We decided that we won't migrate to Angular, but to either React or Vue.js. Eventually we decided to migrate to React for the following reasons:

    1. Many in our community are already using React internally and will be able to contribute.
    2. Using react2angular we can do the migration gradually over time instead of having to invest in a big rewrite while halting feature development.

    So far the gradual strategy pays off and in the last 3 major releases we already shipped React code in the Angular.js application.

    See more

    related Vue.js posts

    Jeyabalaji Subramanian
    Jeyabalaji Subramanian
    CTO at FundsCorner · | 21 upvotes · 158.1K views
    atFundsCornerFundsCorner
    JavaScript
    JavaScript
    HTML5
    HTML5
    Vue.js
    Vue.js
    Vuetify
    Vuetify
    Amazon Cognito
    Amazon Cognito

    At FundsCorner, when we set out to pick up the front-end tech stack (around Dec 2017), we drove our decision based on the following considerations:

    (1) We were clear that we will NOT have a hybrid app. We will start with Responsive Web & once there is traction, we will rollout our Android App. However, we wanted to ensure that the users have a consistent experience on both the Web & the App. So, the front-end framework must also have a material design component library which we can choose from.

    (2) Before joining FundsCorner as a CTO, I had already worked with Angular. I enjoyed working with Angular, but I felt that I must choose something that will provide us with the fastest time from Concept to Reality.

    (3) I am strong proponent of segregating HTML & JavaScript. I.e. I was not for writing or generating HTML through JavaScript. Because, this will mean that the Front-end developers I have to hire will always be very strong on JavaScript alongside HTML5 & CSS. I was looking for a Framework that was on JavaScript but not HEAVY on JavaScript.

    (3) The first iteration of the web app was to be done by myself. But I was clear that when someone takes up the mantle, they will be able to come up the curve fast.

    In the end, Vue.js and Vuetify satisfied all the above criteria with aplomb! When I did our first POC on Vue.js I could not believe that front-end development could be this fast. The documentation was par excellence and all the required essentials that come along with the Framework (viz. Routing, Store, Validations) etc. were available from the same community! It was also a breeze to integrate with other JavaScript libraries (such as Amazon Cognito).

    By picking Vuetify, we were able to provide a consistent UI experience between our Web App and Native App, besides making the UI development ultra blazing fast!

    In the end, we were able to rollout our Web App in record 6 weeks (that included the end to end Loan Origination flow, Loans management system & Customer engagement module). www.jeyabalaji.com

    See more
    Tim Nolet
    Tim Nolet
    Founder, Engineer & Dishwasher at Checkly · | 20 upvotes · 389.6K views
    atChecklyHQChecklyHQ
    Heroku
    Heroku
    Docker
    Docker
    GitHub
    GitHub
    Node.js
    Node.js
    hapi
    hapi
    Vue.js
    Vue.js
    AWS Lambda
    AWS Lambda
    Amazon S3
    Amazon S3
    PostgreSQL
    PostgreSQL
    Knex.js
    Knex.js
    vuex
    vuex

    Heroku Docker GitHub Node.js hapi Vue.js AWS Lambda Amazon S3 PostgreSQL Knex.js Checkly is a fairly young company and we're still working hard to find the correct mix of product features, price and audience.

    We are focussed on tech B2B, but I always wanted to serve solo developers too. So I decided to make a $7 plan.

    Why $7? Simply put, it seems to be a sweet spot for tech companies: Heroku, Docker, Github, Appoptics (Librato) all offer $7 plans. They must have done a ton of research into this, so why not piggy back that and try it out.

    Enough biz talk, onto tech. The challenges were:

    • Slice of a portion of the functionality so a $7 plan is still profitable. We call this the "plan limits"
    • Update API and back end services to handle and enforce plan limits.
    • Update the UI to kindly state plan limits are in effect on some part of the UI.
    • Update the pricing page to reflect all changes.
    • Keep the actual processing backend, storage and API's as untouched as possible.

    In essence, we went from strictly volume based pricing to value based pricing. Here come the technical steps & decisions we made to get there.

    1. We updated our PostgreSQL schema so plans now have an array of "features". These are string constants that represent feature toggles.
    2. The Vue.js frontend reads these from the vuex store on login.
    3. Based on these values, the UI has simple v-if statements to either just show the feature or show a friendly "please upgrade" button.
    4. The hapi API has a hook on each relevant API endpoint that checks whether a user's plan has the feature enabled, or not.

    Side note: We offer 10 SMS messages per month on the developer plan. However, we were not actually counting how many people were sending. We had to update our alerting daemon (that runs on Heroku and triggers SMS messages via AWS SNS) to actually bump a counter.

    What we build is basically feature-toggling based on plan features. It is very extensible for future additions. Our scheduling and storage backend that actually runs users' monitoring requests (AWS Lambda) and stores the results (S3 and Postgres) has no knowledge of all of this and remained unchanged.

    Hope this helps anyone building out their SaaS and is in a similar situation.

    See more
    Select2 logo

    Select2

    2.7K
    16
    0
    2.7K
    16
    + 1
    0
    The jQuery replacement for select boxes
      Be the first to leave a pro
      Select2 logo
      Select2
      VS
      Zepto logo
      Zepto
      Prototype logo

      Prototype

      2.1K
      20
      0
      2.1K
      20
      + 1
      0
      Prototype JavaScript framework
        Be the first to leave a pro
        Prototype logo
        Prototype
        VS
        Zepto logo
        Zepto

        related Prototype posts

        Kir Shatrov
        Kir Shatrov
        Production Engineer at Shopify · | 18 upvotes · 189.4K views
        atShopifyShopify
        jQuery
        jQuery
        JavaScript
        JavaScript
        React
        React
        TypeScript
        TypeScript
        Prototype
        Prototype
        #FrameworksFullStack
        #Languages

        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
        YUI Library logo

        YUI Library

        1.8K
        8
        0
        1.8K
        8
        + 1
        0
        Open Source JavaScript library for building richly interactive web applications
          Be the first to leave a pro
          YUI Library logo
          YUI Library
          VS
          Zepto logo
          Zepto
          Create React App logo

          Create React App

          510
          441
          1
          510
          441
          + 1
          1
          Create React apps with no build configuration
          Create React App logo
          Create React App
          VS
          Zepto logo
          Zepto

          related Create React App posts

          Francisco Quintero
          Francisco Quintero
          Tech Lead at Dev As Pros · | 13 upvotes · 260.2K views
          atDev As ProsDev As Pros
          Google Maps
          Google Maps
          React
          React
          Create React App
          Create React App
          Bootstrap
          Bootstrap
          Keen
          Keen