any system of record has a requirement to be bitemporal, it just isn't discovered until too late IME. I don't know if there's a system anywhere which conciously decided to not be bitemporal during initial design.
The last few months we've seen the fall- or acquisitions of services such as internal.io, dynaboard.com, Uiflow, AWS honeycode, Disha, Skuid, spreadsheet.com[], and some low-code BaaS I don't recall the name of.
Where do you see yourselves compared to these services? I think businesses and devs grow ever-more considerate of the non-(F)OSS services they use.
[]not the same, but they have no-code as one of their main selling points
If you have the Fitbit Ionic or Versa, you could develop your own watch app and companion app, where the watch app will extract sensor data and websocket it to the companion app, which in turn could pass the data to your own backend/database. The API documentation is quite good from Fitbit.
Usually headless in this context refers to content being exposed through APIs instead of a generated user-facing frontend. This way, you can develop the user-facing frontend in whatever frontend libraries and frameworks you want and just consume and expose the CMS content through APIs, and you can use the same APIs to expose content in mobile apps etc...
A typical example of a non-headless CMS is Wordpress where you get the admin panel for content management, _and_ a user-facing frontend for end-users to consume the content.
I only learned about Jasonette a couple of months ago and it's interesting how in some areas both Engine and Jasonette intersect.
When comparing to Jasonette, Engine has a built-in design system and any data fetching / processing is done completely server side. All templates are versioned and stored on the server making it very easy to iterate / A/B test on a live product.
First off, thanks for all your work with the Ionic framework! I use it in education as part of an undergraduate course on cross-platform development, and the students thoroughly enjoy the developer experience.
Question: Do you have an ETA for release of the "Web Componentized" Ionic components? So looking forward to it, especially the potential of teaching e.g. Vue + Ionic components instead of having to put so much focus and effort on teaching Angular (which is a great framework, but requires a lot).
Our testing and shown that it works in IE11 and above. Both Safari and Chrome support custom elements natively, so no polyfill is required. Additionally, Edge has it under construction, and Firefox has custom elements behind a flag. For Edge, IE and Firefox the polyfills are downloaded on demand, rather than every browser always downloading every polyfill.
