All rightey then.
I also, as I have noted, am buying several lanterns committed to in the very infancy of the project. It is getting very old to keep seeing āalternety should not be allowed to have one of these lanterns [or Q8s] ā in various formats. I consider them very very rude. Regardless of opinion; alternety is neither stupid or nor uneducated. I too am an engineer. Engineers have a gene that requires them to evaluate everything. And, if necessary, fix it.
I believe most of what I have written makes sense. That is why I write it. But the regulars despise/attack it. Fine. Everyone gets to put in their two cents (I think).
I honestly donāt know what was rude about my last post. To those I have hideously harmed psychologically ; my apologies. And I have fixed lamp/lantern in my last post. My fault. Lack of precision. I hate it when that happens.
However, may I suggest actually thinking about some of the points and trying to understand the basis and results being discussed rather than having your knee jerk. I understand it is late in the project. I have provided input much earlier. To no avail. But hope springs eternal. I am trying to point out some possible issues or improvements with minimal impact. And improve overall user utility/complexity.
I made a suggestion earlier about polling the buyers of the >1000 lanterns about features. There is a skilled core development group working on this. Their uncompensated work is irreplaceable and deserves kudos. My point about polling is to survey the unwashed masses view of what is useful, required, or not wanted. Logically, there are a lot of potential buyers that simple do not participate in (or understand) the definitions of the lantern. They just want the lantern; whatever. Rather than build a complex (and potentially more expensive) lantern for a subset of potential users; go for most useful and lowest reasonable cost. Reverse the point of view. Simple now; complex next rather than complex now and simple later. This has significant marketing issues. If people buy them and can not deal with the interface (and price), the sales for the manufacturer will suffer. That is rather important to ongoing projects with the offshore manufacturer. They have to make money. Two or more versions can be a significant advantage to the manufacturer. They have a price/performance range. It also determines the future willingness to deal with this sites projects.
Using the Q8 (I own several) as an example. In my opinion (from several experiments) the interface for untrained users is quite hostile. Alternate views of this are completely useless, but widely propagated. Using multiple test persons, regardless of what the designers and (skilled) web site users say, numerous people explain the interface as simple, it just needs to be understood/learned. Others view the interface as incomprehensible. There is a serious dejvue element here.
Asking the potential lantern buyers what they consider important would provide guidance to the development team. Again, I have not gone through and counted everyoneās wish list. Assigning a projected price (or impacts on other features) for the various build decisions in the poll would help map the buyer base into more understandable desires/requirements. It is not too late to do this. But there is a high probability of no one paying attention. I keep getting chastised for not seeing/understanding the ācorrectā configuration. The control of the design, if I understand correctly, is in the hands of a relatively small group. They are absolutely essential. No argument there. But do they serve the masses or their excitement about bells and whistles? I do understand the basis of the web site thread and the anticipated configuration. But configuration has become complicated for civilians.
IT IS A LANTERN should be a battle cry of the relatively unknowledgeable people lining up for the lights (yeah, they are lights).