I tried “forgotten” frameworks — and shipped a client app in 3 hours
I didn't expect to use Framework7 or NativeScript in 2026. But yesterday evening, I got a small client requirement: a simple inventory tracking system. Two roles: Admin -> add items, restock, ed...

Source: DEV Community
I didn't expect to use Framework7 or NativeScript in 2026. But yesterday evening, I got a small client requirement: a simple inventory tracking system. Two roles: Admin -> add items, restock, edit/delete, view audit logs. Staff -> only deduct/sell items. The usual instinct My first thought was obvious: React Native or Jetpack Compose But then I paused. That meant setting up environments, fixing dependencies, dealing with configs, and running npx expo install --fix type commands. And for what? A simple app. I didn't need the best stack; I needed the fastest path to working software. Trying NativeScript I had seen NativeScript before in a YouTube video, so I gave it a try. And honestly, NativeScript felt closer to native and more fluid. The UI felt smooth and the experience was solid. But... It works really well when it works. But when it doesn't, you are kind of on your own. I ran into: inconsistent documentation outdated packages (6-8 years old) issues with font icons not renderi