Eventually you discover that the bugs you create in your code have more to do with karma than skill. Once you develop the skill to code there is no reason for there to be bugs. It is through clearing out the karma that your development ability becomes more and more unhindered. Bugs point to what remains.
As the time approaches to once again put together a mobile app the obvious question is, “What is the latest and greatest way to develop an app that will run on all mobile platforms?”. Only a couple years old, Google is on the leading edge with Flutter!
I can’t wait to get started! Take a look:
Taiga.io is an open source product offering Scrum, Kanban, & issue tracking among other features. It is comparable to Jira, though smaller scale. I’ve enjoyed using this product for years for tracking my software projects and other personal goals. The product can be managed by others at cost, or installed locally for free.
Given that the one mobile app (created by a third party) is rather expensive I’ve decided to initially create some PowerShell cmdlets to access the Taiga REST interface, and later put together a mobile app offering just a few features initially such as marking a user story complete, adding a user story, and adding detail to a user story.
In this way Taiga will be usable easily as a Trello-type app replacement, and in doing so can ensure IP is kept safe.
I’ve started this process with creating an installation video which over time will hopefully lead to increased usage of the product:
ASP.NET Core Identity provides common Authentication features such as a registering a new user with email verification, multi-factor authentication, using external authentication providers such as Google & Facebook, and much more. ASP.NET Core Identity maintains its own database tables, and can be seen as somewhat of an enclosed isolated system.
However, ASP.NET Core Identity has, from the start, been intended to be used to provide a web-based user interface. But, what if we want to integrate many of those features via a WebAPI? Perhaps later, we might even want to take advantage of the provided user interfaces…
Introducing IdentityServer4. IdentityServer4 is designed to provide Authentication as a Service & Access Control for APIs. IdentityServer can be used to get the access tokens needed to consume our webapi.
Turns out IdentityServer4 is able to use the tables provided by ASP.NET Core Identity (see ASP.NET Identity Support). Combining these two let’s us implement a perfect solution from 5 years ago posted here, now in just a few lines of code.
Modern presentation on the web app stack by Dominic Baier (co-creator of IdentityServer4 for last 10 years): https://vimeo.com/369311388
REST API can be seen here: Swagger
Once committed to an eventing technique, in this case a Firebase-style notification via WebSockets, development could commence.
Though there is still much to do the basic design is in place, solo & multi-player games are available and playable.
The current method of authenticating via Microsoft’s IdentityModel can later be used to integrate with logins via Facebook, Google, etc…