fcm VS Ionic Framework

Most of the setup has been completed so now we can dive into some code. First, let's setup Firebase with Ionic-Vue. To do this we're going to need the capacitor community fcm package which can be found here. Once you've installed the package you'll need to go into Xcode and inside your project click on the AppDelegate file and import firebase like so:

To begin, we need to install Capacitor Firebase Cloud Messaging plugin. You can do with a simple command: npm i @capacitor-community/fcm

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?