Alternatives to Vue CLI logo

Alternatives to Vue CLI

Webpack, Meteor, Nuxt.js, npm, and Create React App are the most popular alternatives and competitors to Vue CLI.
383
393
+ 1
3

What is Vue CLI and what are its top alternatives?

Vue CLI aims to be the standard tooling baseline for the Vue ecosystem. It ensures the various build tools work smoothly together with sensible defaults so you can focus on writing your app instead of spending days wrangling with config.
Vue CLI is a tool in the Front-End Frameworks category of a tech stack.
Vue CLI is an open source tool with 27.9K GitHub stars and 5.6K GitHub forks. Here鈥檚 a link to Vue CLI's open source repository on GitHub

Top Alternatives to Vue CLI

  • Webpack

    Webpack

    A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff. ...

  • Meteor

    Meteor

    A Meteor application is a mix of JavaScript that runs inside a client web browser, JavaScript that runs on the Meteor server inside a Node.js container, and all the supporting HTML fragments, CSS rules, and static assets. ...

  • Nuxt.js

    Nuxt.js

    Nuxt.js presets all the configuration needed to make your development of a Vue.js application enjoyable. You can use Nuxt.js for SSR, SPA, Static Generated, PWA and more. ...

  • npm

    npm

    npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day. ...

  • Create React App

    Create React App

    Create React apps with no build configuration.

  • Angular CLI

    Angular CLI

    A command-line interface tool that you use to initialize, develop, scaffold, and maintain Angular applications. You can use the tool directly in a command shell, or indirectly through an interactive UI such as Angular Console. ...

  • Bootstrap

    Bootstrap

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

  • Modernizr

    Modernizr

    It鈥檚 a collection of superfast tests or detects as we like to call them which run as your web page loads, then you can use the results to tailor the experience to the user. It tells you what HTML, CSS and JavaScript features the user鈥檚 browser has to offer. ...

Vue CLI alternatives & related posts

Webpack logo

Webpack

25.9K
17.8K
750
A bundler for javascript and friends
25.9K
17.8K
+ 1
750
PROS OF WEBPACK
  • 308
    Most powerful bundler
  • 182
    Built-in dev server with livereload
  • 143
    Can handle all types of assets
  • 87
    Easy configuration
  • 20
    Laravel-mix
  • 4
    Overengineered, Underdeveloped
  • 2
    Makes it easy to bundle static assets
  • 2
    Webpack-Encore
  • 1
    Better support in Browser Dev-Tools
  • 1
    Redundant
CONS OF WEBPACK
  • 11
    Hard to configure
  • 2
    Spaghetti-Code out of the box
  • 2
    SystemJS integration is quite lackluster
  • 2
    Loader architecture is quite a mess (unreliable/buggy)
  • 2
    Fire and Forget mentality of Core-Developers
  • 2
    No clear direction

related Webpack posts

Jonathan Pugh
Software Engineer / Project Manager / Technical Architect | 25 upvotes 路 1.4M 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
Johnny Bell
Software Engineer at Weedmaps | 19 upvotes 路 1.2M views

So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

See more
Meteor logo

Meteor

1.8K
1.6K
1.7K
An ultra-simple, database-everywhere, data-on-the-wire, pure-Javascript web framework
1.8K
1.6K
+ 1
1.7K
PROS OF METEOR
  • 250
    Real-time
  • 197
    Full stack, one language
  • 181
    Best app dev platform available today
  • 153
    Data synchronization
  • 151
    Javascript
  • 117
    Focus on your product not the plumbing
  • 106
    Open source
  • 105
    Hot code pushes
  • 100
    Live page updates
  • 92
    Latency compensation
  • 38
    Ultra-simple development environment
  • 29
    Smart Packages
  • 28
    Real time awesome
  • 23
    Great for beginners
  • 22
    Direct Cordova integration
  • 16
    Better than Rails
  • 15
    Less moving parts
  • 13
    It's just amazing
  • 10
    Blaze
  • 8
    Great community support
  • 8
    Plugins for everything
  • 6
    One command spits out android and ios ready apps.
  • 5
    It just works
  • 5
    0 to Production in no time
  • 4
    Is Agile in development hybrid(mobile/web)
  • 4
    Easy deployment
  • 4
    Coding Speed
  • 4
    You can grok it in a day. No ng nonsense
  • 2
    AngularJS Integration
  • 2
    Easy yet powerful
  • 2
    One Code => 3 Platforms: Web, Android and IOS
  • 1
    High quality, very few bugs
  • 1
    Easy Setup
  • 1
    Free
  • 1
    Nosql
  • 1
    Hookie friendly
  • 1
    Community
  • 1
    Friendly to use
  • 1
    Stack available on Codeanywhere
  • 1
    Real time
CONS OF METEOR
  • 4
    Hard to debug issues on the server-side
  • 4
    Heavily CPU bound
  • 4
    Does not scale well

related Meteor posts

Lucas Litton
Director of Strategy at DigitalSignal | 13 upvotes 路 174.8K views

Next.js is probably the most enjoyable React framework our team could have picked. The development is an extremely smooth process, the file structure is beautiful and organized, and the speed is no joke. Our work with Next.js comes out much faster than if it was built on pure React or frameworks alike. We were previously developing all of our projects in Meteor before making the switch. We left Meteor due to the slow compiler and website speed. We deploy all of our Next.js projects on Vercel.

See more
Shared insights
on
Meteor
Node.js
at

Mixmax was originally built using Meteor as a single monolithic app. As more users began to onboard, we started noticing scaling issues, and so we broke out our first microservice: our Compose service, for writing emails and Sequences, was born as a Node.js service. Soon after that, we broke out all recipient searching and storage functionality to another Node.js microservice, our Contacts service. This practice of breaking out microservices in order to help our system more appropriately scale, by being more explicit about each microservice鈥檚 responsibilities, continued as we broke out numerous more microservices.

See more
Nuxt.js logo

Nuxt.js

1.1K
1K
243
The Vue.js Framework
1.1K
1K
+ 1
243
PROS OF NUXT.JS
  • 37
    SSR
  • 33
    Automatic routes
  • 22
    Middleware
  • 20
    Hot code reloading
  • 16
    SPA
  • 16
    Easy setup, easy to use, great community, FRENCH TOUCH
  • 16
    Static Websites
  • 14
    Plugins
  • 12
    Code splitting for every page
  • 10
    Automatic transpilation and bundling (with webpack and
  • 10
    Custom layouts
  • 8
    Modules ecosystem
  • 7
    Easy setup
  • 6
    Pages directory
  • 6
    Vibrant and helpful community
  • 6
    Amazing Developer Experience
  • 3
    Not React
  • 1
    Its Great for Team Development
CONS OF NUXT.JS
    Be the first to leave a con

    related Nuxt.js posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH | 19 upvotes 路 571.5K 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
    Giordanna De Gregoriis
    Jr Fullstack Developer at Stefanini Inspiring | 7 upvotes 路 8.6K views

    TL;DR: Shall I keep developing with Nuxt.js 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

    Long version: We have an old web application running on AngularJS and Bootstrap for frontend. It is mostly a user interface to easily read and post data to our engine.

    We want to redo this web application. Started from scratch using the newest version of Angular 2+ and Material Design for frontend. We haven't even finished rewriting half of the application and it is becoming dreadful to work on.

    • The cold start takes too much time
    • Every little change reload the whole page. Seconds to minutes of development lost looking at a loading blank page just changing css
    • Code maintainability is getting worse... again... as the application grows, since we must create everytime 5 files for a new page (html, component.ts, module.ts, scss, routing.ts)

    I'm currently trying to code a Proof of Concept using Nuxt.js and Tailwind CSS. But the thing is, Vue.js 3 is out and has interesting features such as the composition API, teleport and fragments. Also we wish to use the Vite frontend tooling, to improve our time developing regardless of our application size. It feels like a better alternative to Webpack, which is what Nuxt 2 uses.

    I'm already trying Nuxt.js with the nuxt-vite experimental module, but many nuxt modules are still incompatible from the time I'm posting this. It is also becoming cumbersome not being able to use teleport or fragments, but that can be circumvented with good components.

    What I'm asking is, what should be the wisest decision: keep developing with Nuxt 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

    See more
    npm logo

    npm

    60.9K
    46.2K
    1.6K
    The package manager for JavaScript.
    60.9K
    46.2K
    + 1
    1.6K
    PROS OF NPM
    • 649
      Best package management system for javascript
    • 382
      Open-source
    • 327
      Great community
    • 147
      More packages than rubygems, pypi, or packagist
    • 112
      Nice people matter
    • 5
      Audit feature
    • 4
      Good following
    • 4
      As fast as yarn but really free of facebook
    • 1
      Stability
    • 1
      Super fast
    CONS OF NPM
    • 5
      Bad at package versioning and being deterministic
    • 4
      Problems with lockfiles
    • 3
      Node-gyp takes forever
    • 1
      Super slow

    related npm posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH | 24 upvotes 路 1.7M 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鈥檚 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
    Johnny Bell
    Software Engineer at Weedmaps | 19 upvotes 路 1.2M views

    So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

    So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

    The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

    I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

    Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

    I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

    See more
    Create React App logo

    Create React App

    850
    802
    4
    Create React apps with no build configuration
    850
    802
    + 1
    4
    PROS OF CREATE REACT APP
    • 2
      No config, easy to use
    • 2
      Maintained by React core team
    CONS OF CREATE REACT APP
    • 1
      No SSR

    related Create React App posts

    Adebayo Akinlaja
    Engineering Manager at Andela | 22 upvotes 路 627.4K views

    I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen鈥攕ince I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

    A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

    In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

    If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

    See more

    I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

    We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

    Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis 聽for cache and other time sensitive operations.

    We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

    Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

    See more
    Angular CLI logo

    Angular CLI

    737
    583
    0
    A command line interface for Angular
    737
    583
    + 1
    0
    PROS OF ANGULAR CLI
      Be the first to leave a pro
      CONS OF ANGULAR CLI
        Be the first to leave a con

        related Angular CLI posts

        Vaibhav Taunk
        Team Lead at Technovert | 31 upvotes 路 1.5M views

        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

        Picked Angular 2 as framework since Angular CLI made it easy to get started on a self-contained frontend web project with TypeScript for easier development -- thanks to intellisense extensions for Visual Studio Code, hassle-free browser compatibility with the built-in Babel transpiler and packaging with the built-in Webpack configuration.

        See more
        Bootstrap logo

        Bootstrap

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

        related Bootstrap posts

        Ganesa Vijayakumar
        Full Stack Coder | Module Lead | 18 upvotes 路 2.3M 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 路 695K 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
        Modernizr logo

        Modernizr

        25.9K
        1.2K
        0
        Respond to your user鈥檚 browser features
        25.9K
        1.2K
        + 1
        0
        PROS OF MODERNIZR
          Be the first to leave a pro
          CONS OF MODERNIZR
            Be the first to leave a con

            related Modernizr posts