When i first discovered the Dwarf2 i really wanted it but i already had a celestron avx and a relatively good scope.
Then i almost hit the buy button. And then i discovered the SeestarS50 and then it was diffcult to choose. Long storry short... I ended up with the Seestar and i was quite happy.
Now that i have the Seestar there has been several upgrades. The biggest upgrades was not in the announcements of functions. So this is a big plus.
Zwo seems to be listening and im sure that they have implemented stuph earlier than planned. And as a developer i know that this can bite you in the tail later on.
I have read a little about the Dwarf3 and comparing it with the S50 it seems that the biggest differences are:
Hardware: More storage
Software: they got "plan and capture", "astro mosaic" , "night mode capture(remove the ir filter)" and "panorama stitching"
So i guess Zwo has to listen to the customer and also stay in focus and not implement new things to fast.
And what is to fast? Customers wants stuph now but developers need time to implement, test and then let a limited pool of beta testers check before pushing a new release.
So maybe try to priority:
- Fix reported bugs and/or refine functions
- Find out how long time developers need to i.e add a "plan and capture" or "astro mosaic". Start with what the developers think need little time to implement. Then release to beta testers. when they are happy make a new release.
Doing so big functions can be released much quicker if they have limited developers or have limited "funds" linked to making more functions.
But what do users want first? "plan and capture", "night mode pictures" or "astro/regular mosaic"?
A "store to dropbox/gdrive/onedrive" function could solve the S50 low storage when taking several hours of a nebula as long as you have Internet.
But yes Zwo should probably make some hints about expected timelines for some functions.