bottleneck
Choose style:

Author Topic: What should we call our next generation Almond?  (Read 13395 times)

0 Members and 1 Guest are viewing this topic.

Offline Ohiomedic

  • Backer
  • *
  • Posts: 446
  • Thanks: 0
  • Registered : 27/05/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: What should we call our next generation Almond?
« Reply #15 on: November 18, 2014, 04:07:06 pm »
Why would Securifi not correct miserable pending bugs before even thinking new product development. I think as early backer, long time bearing these recurring bugs, the least I expect is to see a full commitement resolving them, not splitting or redirect available resources to other project. Not shure it is a good idea to ask me what will be the name of your next product,

I did a party last weekend and my A+ crash many times stopping streaming music from appletv, tv movie for friends childrens, wifi remote controle and many more, just an nightmare. I now have to rely on something else.  Good luck for your next product...

Taking the home automation and maybe other things, they could both still run on the same basic firmware, so resources wouldn't be split.

Offline gunnm

  • Backer
  • *
  • Posts: 1
  • Thanks: 0
  • Registered : 18/10/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: What should we call our next generation Almond?
« Reply #16 on: November 19, 2014, 02:34:53 pm »
Simply Almond Lite :)

Offline cjansss

  • Backer
  • *
  • Posts: 11
  • Thanks: 0
  • Registered : 20/09/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: What should we call our next generation Almond?
« Reply #17 on: November 20, 2014, 06:34:19 am »
In addition to the Almond+, we're going to be releasing a more affordable product that is an improved version of the original Almond.
We were hoping you guys would be willing to help us make our mind up with regards to the name of this product, so please cast your vote in the poll above.

The new Almond will carry the same overall product design as the original Almond, but we've upgraded the hardware, added a USB 2.0 port, improved the Wi-Fi performance and lastly, we've also added ZigBee support. It should be seen as the little brother to the Almond+ and it will of course be more affordable, but it'll not be less than what we offered the Almond+ for on Kickstarter. It's not based on the original Almond+ hardware and it's still single band Wi-Fi and has 10/100Mbps Ethernet.

I do not understand why Securifi is focusing on a cheaper variant of the Almond+ which is not finished yet? Hardware wise it might make sense to think about it now as it's cheaper to make and more efficient etc but software wise Almond+ is so far from finished hence using it is baseline for a cheaper version feels like a waste of time. Firstly the software on the Almond+ should reach stable and what I mean by that is all features as promised/planned (and thought of along the process) should be finished and all known P0 bugs should be fixed. Does Securifi have enough resources to commit to another product without impacting the Almond+? I understand planning for a new product is done a long time in advance but still.....

Amritendu

  • Guest
Re: What should we call our next generation Almond?
« Reply #18 on: November 20, 2014, 10:46:16 am »
I do not understand why Securifi is focusing on a cheaper variant of the Almond+ which is not finished yet? Hardware wise it might make sense to think about it now as it's cheaper to make and more efficient etc but software wise Almond+ is so far from finished hence using it is baseline for a cheaper version feels like a waste of time. Firstly the software on the Almond+ should reach stable and what I mean by that is all features as promised/planned (and thought of along the process) should be finished and all known P0 bugs should be fixed. Does Securifi have enough resources to commit to another product without impacting the Almond+? I understand planning for a new product is done a long time in advance but still.....

Ok, the attempt is not to make a cheaper version of Almond+ but an improvised version of the first generation Almond (which includes a better range) with an addition of Zigbee module. This should not be interpreted as shifted focus from Almond+ software development to a different product all together! Its just an attempt to provide a better version of the first generation Almond at an affordable price (which is easy since its on the same platform of the first generation Almond) and is by no means taking our focus off the Almond+.

Offline xaminmo

  • Backer
  • *
  • Posts: 45
  • Thanks: 2
  • Registered : 13/10/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: What should we call our next generation Almond?
« Reply #19 on: December 05, 2014, 10:59:25 pm »
I think "Almond Lite" would be very marketable, logical, and much more reasonable than a date or a version number.
Geek, pilot, cyclist, parent.

Offline mixmaven

  • Backer
  • *
  • Posts: 3
  • Thanks: 0
  • Registered : 22/08/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: What should we call our next generation Almond?
« Reply #20 on: December 06, 2014, 01:27:15 am »
I think "Almond Lite" would be very marketable, logical, and much more reasonable than a date or a version number.
I like Almond Lite!
or
Almond One
Almond (-) or (Almond)
Cashew

What about Mounds?
iAlmond Air??
Almond Brothers???
;)

Offline kenny113

  • Backer
  • *
  • Posts: 13
  • Thanks: 0
  • Registered : 12/08/2014
    YearsYearsYearsYearsYearsYearsYearsYearsYearsYears
Re: What should we call our next generation Almond?
« Reply #21 on: December 23, 2014, 05:02:06 pm »
I like, "We're worried about marketing a new product before we finish working on a product we shipped extremely late of schedule yet somehow so extremely early in the development cycle that most of the features don't exist...let alone the device working out of the box!"

Whew, that was a mouthful...

Or just call it "Almond: Junk Edition"... Oh wait... That already exists as the Almond+

 

Page created in 0.06 seconds with 21 queries.

bottleneck