Bootstrap vs NativeScript: What are the differences?
What is Bootstrap? Simple and flexible HTML, CSS, and JS for popular UI components and interactions. Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web.
Bootstrap belongs to "Front-End Frameworks" category of the tech stack, while NativeScript can be primarily classified under "Cross-Platform Mobile Development".
Some of the features offered by Bootstrap are:
- Preprocessors: Bootstrap ships with vanilla CSS, but its source code utilizes the two most popular CSS preprocessors, Less and Sass. Quickly get started with precompiled CSS or build on the source.
- One framework, every device: Bootstrap easily and efficiently scales your websites and applications with a single code base, from phones to tablets to desktops with CSS media queries.
- Full of features: With Bootstrap, you get extensive and beautiful documentation for common HTML elements, dozens of custom HTML and CSS components, and awesome jQuery plugins.
On the other hand, NativeScript provides the following key features:
- 100% Access to Native Platform API
- NativeScript is free of charge as an open source project
"Responsiveness" is the primary reason why developers consider Bootstrap over the competitors, whereas "Access to the entire native api" was stated as the key factor in picking NativeScript.
Bootstrap and NativeScript are both open source tools. It seems that Bootstrap with 134K GitHub stars and 66K forks on GitHub has more adoption than NativeScript with 17.2K GitHub stars and 1.27K GitHub forks.
According to the StackShare community, Bootstrap has a broader approval, being mentioned in 7046 company stacks & 1115 developers stacks; compared to NativeScript, which is listed in 9 company stacks and 26 developer stacks.
What is Bootstrap?
What is NativeScript?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using NativeScript?
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
So, i am preparing to adopt NativeScript.
For years my hybrid projects used Apache Cordova.
"Let's avoid to maintain two teams and double the deliver velocity".
It was good for a few years, we had those september issues, (i.e. apple broke some backward compatibility) , but for the last years, things seems to be losing the grip faster.
Last breaking changes, for instance, seems to have a workaround, however that growing feeling that simple things can not rely on so fragile webviews keeps growing faster and faster.
I've tested nativescript not only on it's "helloworld", but also on how do they respond on issues.
I got tweed support. I opened an github issue and got answers on less than 10 hours (yes i did it on another timezone and very close to a weekend). I saw the faulty docs get corrected in two days.
The bad news is i only can adopt nativescript on newer projects, since there is no budget to revamp the current solutions.
The good news is i can keep coding on Vue.js , without vou router, but that's ok. I've already exchanged vanilla html for real native app with background magic enabled, the router can be easily reproduced.
ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling
import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.
React Helmet was chosen to handle
<head> content, because it works universally, making it easy to throw back the correct
<title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.
<style> tags when using #StyledComponents.
React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.
Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.
It is using the native components to build the UI and offers the best skills reuse story. All you need to know is JS/TS and CSS. Angular 2 is also supported which leads to even more code reuse across web and mobile.This is also the best way to access the native platform APIs directly.
NativeScript allows you to reuse your JS skills to build Native mobile apps without any sacrifices. It takes a bit to learn about all possible features, but each time you discover a new one you can't help but get more and more excited.
We have been using it for the past 3 years and have no complaints
Good service with a good price, worth the money.
Leanstack was on Bootstrap 2. Chose this because it is wildly popular, so it’s active, has been used a lot in production, and has a ton of features. Anything you need to do from a UI perspective, there’s likely a plugin for it already part of the library. Haven’t tried the others, but we're happy with BS.
For StackShare, we upgraded to Bootstrap 3. I don’t like that they changed the name of columns, essentially breaking the grid layout for Bootstrap 2 and below, so that was a real pain to update. I hope they don’t do that again. Once we have more bandwidth, we’re totally going to decouple our markup from Bootstrap.
We started with a bootstrap based template and then completely rewrote it due to poor design of the template. Using boostrap properly was a great experience - once you learn it and use it properly, it's simple to use and very good at being responsive and adapting to the various screen view.
I simply bought a "job board" template for the website, which is written using Bootstrap 2. I'm hoping to upgrade the site to Boostrap 3 when I'll have a time.
Я просто купил шаблон для доски вакансий, написанный на Boostrap 2. Когда будет время перепишу все на Bootstrap 3.