Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:blog [2026/03/06 18:55] – [Conference Mode] darkgrueen:blog [2026/08/31 20:35] (current) – [New Product News] darkgrue
Line 1: Line 1:
-{{ :en:news_fox_for_docs.tailco_copy.jpg?600 |}}+====== Blog and News ======
  
  
-====== Blog and News ======+===== August 30, 2026: Launch Imminent! ===== 
 + 
 +==== New App Development Changes ==== 
 + 
 +Code-L, our application developer, has been busy updating The Tail Company app during this time. 
 + 
 +  * Over-The-Air (OTA) update support has been rewritten, and now supports linking OTA files to hardware versions, and having a minimum app version. 
 +  * Also, Android Wear support is currently being worked on. Unfortunately, while the app framework supports cross-platform development for Android and iPhone, no such cross-platform support exists yet for cross-platform watch development, so Apple Watch support will have to be a separate effort. And watch development is itself a completely different thing than doing development for the phones. 
 +  * Lastly, internal state management for the app has been completely overhauled, everything that holds state is now a singleton class with a state variable. 
 +  * New product support is already included. 
 +  * New look and feel! 
 + 
 + 
 +==== New Firmware Development Changes ==== 
 + 
 +Development of TailControl, our product firmware platform, has not stood still. The addition of a new product (more on that later) required some pretty significant code refactoring to support new hardware and a new movement subsystem. That resulted in better-organized code and significantly improved internals. 
 + 
 +But as the new product development progressed, it became clear that managing the problems created by being pinned to an older Arduino and ESP-IDF would not just create problems in the future, as support libraries moved forward with their own development, it was creating issues with timer management and other incompatibilities surfaced by the new product hardware being folded in. So this kicked off a search for a solution that allows us to keep the existing PlatformIO tooling, but also keeps pace with the Espressif ecosystem. (p)eople (i)nitiated (o)ptimized (arduino), pioarduino, fit the bill nicely. But jumping forward into a new major version meant a good amount of refactoring as well to accommodate API changes. In the end, the effort should pay off with better codebase maintainability and reliability. 
 + 
 +  * Migrated from the PlatformIO Espressif 32 development platform to pioarduino. This moves us from the Espressif IoT Development Framework (ESP-IDF) v4.4.7 and Arduino v2.0.17 core to ESP-IDF v5.5.2.260206 and Arduino v3.3.7. This gives us access to latest Arduino Core and ESP-IDF, support for newer Espressif hardware, and active maintenance and updates for the development platform. 
 +  * Migrated EarGear 2 to the new channel-based I2S driver. The new driver has better resource management, enhanced power management, simplified duplex communication, and finer control over I2S channel states. 
 +  * Removed dependency on the JLed library and replaced it with a small custom class built directly on Arduino v3's native API that is initialized later in the system setup, rather than immediately. 
 +  * Experimental support for RGB lighting on most products. 
 +  * Many bugfixes. 
 + 
 + 
 +==== Ever wondered how firmware actually gets developed before a product ships? ==== 
 + 
 +Meet the DesqTail - my desktop development platform, and the secret weapon behind our firmware workflow. 
 + 
 +{{ :en:video5116316049750361112.mp4 |}} 
 + 
 +The concept is borrowed from aerospace engineering, where it's known as an "iron bird": a ground-based test rig used to prototype and integrate aircraft systems during the development of new designs. An iron bird is essentially a complete aircraft stripped down to its bones - no fuselage, no superstructure, no seating, none of the non-flight-critical hardware. What remains is every system that actually flies the aircraft, installed and wired up so engineers can test each one individually, and more importantly, in concert with every other system aboard. 
 + 
 +The philosophy is powerful: simulate reality as closely as possible, without the cost and risk of doing it in the air. 
 + 
 +I apply that same philosophy to firmware development through full Hardware-in-the-Loop (HIL) testing. Rather than writing code and hoping it behaves correctly when it finally lands on production hardware, the DesqTail puts real hardware on my desk - running real firmware, in real time. Every product platform we build can be exercised right here, in a controlled environment, before a single unit ships. 
 + 
 +The advantages compound quickly: 
 + 
 +  * Speed - No waiting for test hardware to be assembled or shipped. Iteration cycles shrink from days to minutes. 
 +  * Cost - Catching a firmware bug on the desktop is orders of magnitude cheaper than catching it in the field. 
 +  * Confidence - Full HIL means the firmware isn't being tested in isolation or simulation. It's talking to the actual peripherals, sensors, and interfaces it will live with in production. 
 + 
 +What makes the workflow particularly effective is the immediate feedback loop. While the physical model sits right in front of me - behaving exactly as it would in a deployed unit - I can simultaneously observe live diagnostic output inside the IDE. If something misbehaves, I see it in hardware and in code at the same moment. There's no guesswork about whether a bug is in the firmware logic, the hardware interface, or somewhere in between. 
 + 
 +It's the iron bird principle, scaled down to a workbench - and it changes everything about how reliable firmware gets made. 
 + 
 + 
 +==== New Product News ==== 
 + 
 +There's a new Tail Company product - [[https://thetailcompany.com/paws-with-claws/|Paws with Claws]]! Those of you on the Dev Telegram channel have probably heard me refer to it as "Sekret Project": 
 + 
 +{{ :en:whitepaw.mp4 |}} 
 + 
 +I've had the pleasure of working closely with Master Tailer on this, and I'm directly involved in the entire product design and development - something I hadn't had the opportunity to do until now. 
 + 
 +We've iterated rapidly through a number of different designs quickly. Each new iteration really jumped the design forward and added new features, which was really exciting. We're going into the start of the Kickstarter strong: firmware is feature-complete, and app support is ready. Many prototypes have been built to test out ideas, and we're working on fine-tuning the look and feel This simplifies things down to bulk part orders and The Tail Company can concentrate totally on fulfillment, the design being complete. 
 + 
 +We're really excited about this, and hopefully you will be too! 
 + 
 +Tail Co has also added [[https://thetailcompany.com/product/hypermotion-tails/|Hypermotion Tails]], an affordable, non-electronic moving tail option designed for cosplay, furry events, and alternative fashion. Hypermotion tails are made from a flexible silicone core. So they keep wagging forever! 
 + 
 +And don't forget [[https://thetailcompany.com/product/floor-dragger-tails/|Floor Dragger Tails]], for the largest of non-electronic tails that make a statement that can't be ignored. 
 + 
 + 
 +==== Keep up With The Tail Co ==== 
 + 
 +Make sure to avail yourself of the many Tail Company resources, from the Telegram [[https://t.me/joinchat/VCdXxqKgRv2yrDNC|Tail Co Friends]], [[https://t.me/+5XsaunrTpIc4OWI8|Tail Co Dev Chat]], and [[https://t.me/+E8fERfvkcEI1MTAy|App Translators]]; the [[https://docs.thetailcompany.com/|Technical Wiki]]; or join the cosplay community with [[https://coshub.com/|CosHub]] and the [[https://discord.gg/R2qutAmSXg|CosHub Discord Community]]! 
 + 
 +RAWR! 
 + 
 +Your Friendly Lurking Horror,\\ 
 +**Dark Grue** 
  
 ===== March 1, 2025: TailControl Love Is in The Air! ===== ===== March 1, 2025: TailControl Love Is in The Air! =====