WASM-ImageMagick VS Ionic Framework

Credit: Go check it out the GitHub project page thanks to Nick Maliwacki's (KnicKnic)

Image Conversion via WASM-ImageMagick

I've gone with ImageMagick ported to WebAssembly to do basically the exact same things as with FFMpeg, but with a tiny bit less locking up. In the future I would like to get these things running in multithreaded Web Workers as well as have the ability to easily configure transcode settings to whatever is desired instead of the defaults as it is now.

When it comes to audio/video the trusted tool that is often used on the desktop is FFmpeg and this too has been ported to run in the browser, although if you want multithreading you will need to make sure you have special CORS headers enabled to gain access to the SharedArrayBuffer. For images on desktop there is the popular ImageMagick which indeed also has been ported.

ImageMagick is the go to for these kinda things and apparently there is a WASM version: https://github.com/KnicKnic/WASM-ImageMagick

I was recently able to sit down with some of the core members of Ionic, who also created Stencil a toolchain for building Design Systems and Progressive Web Apps. We talked at great length how typically companies are approaching Ionic from a Design Team and need help building components. As a developer I wanted to talk about the Web Components that are used within the Design System first. There was a decent amount of surprise, so I thought I would break down what a Design System is and why it doesn't matter which end you start with, as long as you have both your Design and Development teams working together to build your Design System.

Look into Ionic Framework https://ionicframework.com/ or Cordova. They might be overkill for what you’re trying to do, but they allow you to create cross-platform apps via html/css/js.

Ionic Framework UI Components are used to build a website and then a mobile application is built using Ionic Capacitor. Ionic UI components are not required but are used for UX. The vue js code presented here will work fine in a separate application.

Welcome to Part Two of this four-part series on building a mobile game using open source technologies. We'll be using Phaser, along with Ionic, Capacitor, and Vue.

Turns out, it's easier than I expected! Thanks to Phaser, along with Ionic, Capacitor, and Vue, I was able to get a mobile game up and running on an iOS device working only a few hours here and there over two weeks.

Ionic Vue tabs navigation when using with child views inside of tabs is broken. The problem is that navigation(routing) using the tabs should be non-linear, but Ionic Vue has an issue with preserving the history track for each of the tabs. The issue is described there. Is there a way to make a non-linear routing stack in Ionic Vue?