Why you should NOT use NativeScript

1. What {NS} promises is a lie

2. Documentation is ridiculous

  • Unanswered questions on StackOverflow
  • Unanswered or zero value answers (“it’s your fault…”) on GitHub
  • Judging you on NativeScript Slack community instead of getting proper help

3. Performance is terrible

4. Arrogant communication

5. There’s no support at all

6. Prepare for continuously refactoring

Final Thoughts

UPDATE: NativeScript 8 upgrade

I wanted to build our Android app, and I’ve got 1000+ error messages as a result…

So if you have a shared-code NativeScript project, you are NOT supported anymore, and you will have to learn the whole thing from scratch OR you have to pay them to solve this issue.

  • have a 100% useless and misleading documentation
  • are changing the core packages continuously between major versions
  • act like a douchebag when you ask their help for free




Oldschool vampire octopus

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How to install v8js on a server running PHP 7.4.3 on a Ubuntu 20.04 environment.

Functions and Game HW

My experience working Vonage API’s as part of a Coding Challenge

First thing was create a Trello Backlog to manage this project

Text-To-Speech Using ResponsiveVoiceJS API

Setting up Jest with React and Phaser

Introduction to React Hooks — useEffect

To do vs Done. Finishing a To do App.

An Oxymoron : Static Analysis of a Dynamic Language (Part 4)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


Oldschool vampire octopus

More from Medium

Kotlin Vs. Flutter-Which Technology Will Rule in 2022

Thoughts On The Flutter Puzzle Hack

The Problem with Flutter and Multi-Platform

Dart Functors, Applicatives, And Monads In Pictures