UI kit VS Quasar Framework

To be able to use the UIKit framework, you can visit the website directly at https://getuikit.com/.

UIkit: A lightweight and modular front-end framework.

Franken UI is compatible with UIkit 3 and can work as a standalone CSS framework but can be integrated with Tailwind CSS for faster styling and customization. The design of Franken UI is influenced by shadcn/ui. It aims to provide a solution to developers who are not comfortable using React, Vue, or Svelte by leveraging UIkit for JavaScript and accessibility.

As an iOS engineer, you've likely encountered SwiftUI and UIkit, two popular tools for building iOS user interfaces. SwiftUI is the new cool kid on the block, providing a clean way to build iOS screens, while UIkit is the older and more traditional way to build screens for iOS. SwiftUI uses a declarative style where you describe how the UI should look, similar to Jetpack Compose in Android. UIkit, on the other hand, uses a drag-and-drop development style, which is relatively similar to Android XML.

All that's left is adding a little style. I won't claim to be a frontend engineer or a UI designer, so I just used UIKit to easily add modern-looking style to the HTML table and buttons. As mentioned throughout the article, the CSS classes and other small details are excluded since they are not directly relevant to the tutorial. See the full example on GitHub to try running it for yourself.

Can try UIKIT out if you're looking around, I've used it solely for some quick slider stuff in certain projects and use it fully in others. The docs are pretty good and they have a discord community that's fairly active.

UIKit is my favourite

I personally like UI Kit, they provide the css and js for basic components that look good. Just use their documentation as a reference, copy and paste the HTML with classes.

ProcessWireProcessWire is a fantastic CMS/CMF (content management framework) and I think it is a good fit for your skills. Works with any front end CSS although my personal preference is UIkitUIkit.

I have a bit of an obsession with finding the fastest way to launch apps. My goal is to be able to create fully functional MVP's and proofs of concept in less than a day. That means being able to spin up a backend and then implement a frontend as efficiently as possible. For the backend, PocketBase has been my favorite lately. On the frontend I am still trying to find a winner. I like Quasar (VueJS + Capacitor) which is fantastic for web apps, but falls a bit short for mobile apps. I've been eyeing React Native lately especially since Expo offers a ton of great plugins like Location and also supports remote updates.

Cool, could also check out a unified App platform framework:

https://quasar.dev/

Cheers =3

In general... it is often a skill issue with labor pools, as firms accepted Java/JavaScript is almost universally known by juniors.

Apps are in user space, and are often disposable-code after 18 months in most cases. Projects like https://quasar.dev/ offer iPhone/Android/iOS/MacOS/Win11 single code base auto-generated App publishing options, but most people never hear of it given a MacOS build host is required for coverage.

The talk pokes fun at the Ivory tower phenomena, and how small-firm logical assumptions halt-and-catch-fire at scale. =3

https://en.wikipedia.org/wiki/Ivory_tower

In general, people must make a choice between portability, and the breadth of optimizations.

For multi-platform builds, there are single code-base frameworks available:

https://quasar.dev/

For MacOS, Linux Gtk, and Windows native builds there are mature free libraries that allow both FOSS and commercial static linking:

https://wxwidgets.org/

Game engines are designed to solve a single set of use-cases for optimization, and portability is usually terrible outside the current windows release.

Best of luck, =3

Quasar. The enterprise-ready cross-platform Vue framework.

I like this for simple mobile projects:

https://quasar.dev/

In some cases, going with an SVG icon pack etc. can save a bit of space. =3

In the previous article we set up the skeleton of the application with the Quasar framework based on VueJS

It is OK, people wouldn't know what is missing if they never saw the alternative.

"It's hard to even parse this sentence"

Try to cross-compile something on modern MacOS, and handle the DRM signing on another platform. For example, you are still going to need an active Apple Developer account to run https://quasar.dev for MacOS/iOS targets, or users are going to incur a bit of hassle running your code.

It is ok, most people have trouble understanding each other at first. =3