Proper Hubitat Elevation documentation in dire need

[maffpt]

@dman2306

I agree with the things you're saying, but let me put my business hat on for a moment. When you release products you release an MVP (Minimum Viable Product). Basically, what's the minimum amount of work you can do and turn a profit?

I can't disagree with this reasoning - Hubitat is a business and the mindset should always be such.

@dman2306

Then over time you enhance it.

Isn't it the time to enhance it? I'll discuss it more ahead in this response.

@dman2306

I agree the documentation is poor at best. However, look at how many apps and drivers have been created using it... There's a ton of cool stuff out there that are pretty complicated! That means it's sufficient to meet HE's goal -- it has created a rich ecosystem of apps/drivers with minimal effort on the part of the HE team to document it.

No questions about that too !

What this community is producing is amazing - everyone is so committed and hardworking and helpful. I'm glad to "land" on this environment.

I started my career more than 40 years ago as a Technical Support Engineer and, in spite of rising through the ranks, I always kept the idea that a good infrastructure, not just sufficient but, for sure not overshooting it, is paramount to support business and I had a quite share of proof that this is a successful approach.

What I can imagine - and hope for - is how more productive the developers would be and more developers could be attracted to HE - again, hope for - if we have at our disposal a better documentation. How many new developers could join the ranks and how more productive could we all be if we have a better documentation available?

@dman2306

he question is, if it's going to take X hours to document it better, how many Y dollars will it generate? My gut says, X = 200-300 hours, and Y = right around $0. So if I were the CEO of Hubitat, this isn't where I'd focus my efforts either. Instead I'd focus on two things - what features are required to increase market share and what additional revenue streams can be created?

As of now, HE is not for the average user. However, I plan use HE hubs as my central strategy for my own Home Automation business and I'll need that it should be as user friendly as possible.

As I suggested in a previous response, why not we, as developers, could be a revenue stream also? I'd be glad in paying an annual fee to be a "Registered developer". I know that it will not be a huge revenue stream and for sure not the main revenue stream, but maybe good enough to support a dedicated team to support the community - and, of course, documenting ...

One of the features of HE that is usually praised on many reviews is its ability to be highly customisable and, in my case, together with the local processing capability and an active community were the main reasons to choose HE as my hub,

@dman2306

Short story is, while selfishly I'd like the documentation to get better (I've submitted dozens of updates to it myself!) at the same time, I can think of a million other priorities that I'd rather HE focus on. Better documentation isn't going to sell more hubs. More consumer friendly features will sell more hubs.

For sure more user friendly features will be highly welcome - and I'll need that. I'm betting on it !

Initiatives like Smartly are great Smartly - the Hubitat dashboard skin engine and I can't wait to use it. For sure a very nice looking and functional dashboard is fundamental to gather clients for my services and Smartly, AFAIK, seems to be really great.

@BrianP

We will get new features and a healthy ecosystem only if they stay in business. If anything, they should be focused on making it easy to set up for non-technical people, without removing the capabilities that make it so lovely for people who have enough knowledge to customize things.

That's why I'm confident that I did a right choice with HE: this community is beyond words - I can never stop praising it.

@BrianP

And the worst thing for developers and consumers is if Hubitat doesn't sell any more hubs!

This is something that worries me: revenue streams. I really wish that Hubitat become a unicorn - everybody will be thrilled with it, no question about that!

@BrianP

We will get new features and a healthy ecosystem only if they stay in business. If anything, they should be focused on making it easy to set up for non-technical people, without removing the capabilities that make it so lovely for people who have enough knowledge to customize things.

I believe, and I'm pretty sure most people here will agree with me, that this community is a huge asset for Hubitat. And I'd like it to grow and I believe that a good documentation would help more developers to come aboard.

@BrianP

The Hubitat Package Manager is a great addition for "aftermarket" apps!

The Hubitat package manager initiative is another example as how important this community for HE. I'll take a close look at it before releasing the app/drivers I'm developing.

Last but not least, thank you guys for taking time discussing this topic.

Peace and health for everybody!