Tetrapad + Tete is pretty fantastic IMO. It's amazingly intuitive to get around despite how ridiculously deep and flexible it is. A bit of a master class in good UI/UX in problem spaces that can only be simplified up to a point.
Since I know there is active development on tete, my greatest hope is to eventually see a more fleshed out "finger drum" mode pulled out from the "Euclidean 0" setting. I wonder how many others feel the same way, and what kind of ideas and suggestions others would have. Apologies of course, if I missed features or possibilities that are already present, or if you think I'm a victim of anti-modular thinking, and am asking for too much from a "single pair" of modules
Some things I'm thinking could be nice in such a mode:
* option for triggers instead of gates - this seems broadly useful, even in the existing Euclidean mode. Quickest I can tap in are still too long to avoid double triggering on things like rings' input. Configurable or variable trigger lengths could be handy, especially for triggering external gear. A multiplier/divider for gate length on a playing sequence could be really cool, but i could see that sort of thing being a stretch in terms of keeping things simple and not overly specific
* a 2-sequence per-pad mode would free up more tracks for those that don't need position CV, and allow for chokes, boolean logic, and other kinds of sync/interaction between two channels
* drum-specific settings like rachets/triplets/accents might clutter things up or fit awkwardly with euclidean mode, but fit well in a dedicated drum mode.
* finer grained attenuation options for outputs could be nice in this mode, designed for interacting with external equipment. 1V steps are already really nice to have built-in, but a lot of external cv/expression gear has ranges like 3.5V, and drum trigger modules can be be pretty finicky with their input tolerances. being able to set a minimum on the range could be useful, if it could be crammed in without overcomplicating things. this stuff could probably be useful for attenuation in general, but i could see it make sense to me to limit it to one mode if it adds unavoidable complication to the UI.
Last, but not least for me, icing on the cake would be for an option for "velocity trigger" outputs - triggers with the amplitude determined via position or pressure. The use case is for external drum trigger modules, like Nord Drum or Roland TM-2, and I'm pretty sure it's been requested before in this thread. Do-able now from Euclidean 0 with a gate-trigger converter and VCA for each channel, but it would be nice not to use up so many of these. This kind of channel would have more general purpose uses, e.g. pinging things like filters and LPGs, or Rings' audio input.
TL;DR: a focused "Drums" mode, more focused on triggers than gates, with consideration given to controlling modules and external gear that's finicky about gate length, gate amplitude, and CV range, would be, in my opinion, an excellent addition to this already excellent pair of modules. Additionally, a separate Drums mode would allow for some additional/complicated features without complicating the UI/UX for existing modes.