Yes. One thing I will definitely say is that I think Evolv need to step up their game in terms of communicating. I don't just mean this whole beta process, I mean post-release. They should publish some detailed information on how the mod works, especially on stuff like TC and the uses of the software. 200W is great for TC? OK, tell us why!
So far as I can tell they published next to nothing around TC on the DNA 40 - I learnt all of what I know from the titbits that came from Evolv via P Busardo, and then far more from the forums. That lead me to some erroneous understandings, for example believing that TC and contact coils were fundamentally incompatible - because that's what Busardo said that Evolv said. (In fact, it's that Ni200 can't have contact coils because it doesn't oxidise - not that they won't ever work for TC, in fact arguably they should work better in metals that support them like Titanium, Resistherm (Alloy 120) and Stainless Steel.)
Compare that to what Dicodes have published, their Application Guide for Temperature Controlled Vaping. It has a wealth of interesting information, a lot of it directly applicable to all TC. This is exactly the sort of stuff Evolv should have published when the tech was new - to my knowledge they didn't publish anything, even really obvious stuff like needing tight connections and reliable ohms. They left that information to trickle down through the big YouTube names and via the forums. This to me suggests a rather limited world view - suggesting that the vaping world consists only of those on forums and YouTube. It doesn't, and nor should we want it to.
Another example: after I saw Busardo comment that there was a new version of the DNA 40 chip with Atty Lock, I looked around for info. Tried Evolv's home page, their Facebook. Could not find a single reference, except mentions on forums. To my knowledge they didn't publish a single public word indicating there even was a new release, let alone that it contained an impotant, asked-for new feature. I suppose they communicated only privately to their vendors and beta testers, and hoped they would spread the word.
I really think this whole aspect needs to change. They need to publish details of what their hardware and software does and how to make the best use of it. They need to clearly announce and describe each new update. They should have a file repository for anything that can imported into the software, like the CSVs as you said.
If they're too busy themselves, they should draft in members of the community. I'm sure there are members of the beta program who are capable technical writers and would be glad to write documentation and updates.
Some of this is acceptable from a small company that's growing, but I think Evolv would think themselves past the 'start up' stage now - and would certainly want outsiders to think that of them. In my view that requires a more professional, open, communication-focused approach.
