@AlyssaWOAH. As @acs pointed out, what about the SDK?.
As for the existing app, sure, I can write comments about the app, such as under “Categories”, why is there a separate category for Rib Eye or Short Ribs and one for Beef? You really don’t need us telling you what those things mean and the difference between the type of meat and the type of cut. Regardless here is my suggestion for categories: 1) Start with the type of meat/food (Beef, Chicken, Fish, Pork, Duck, Lamb, Eggs, etc) and then 2) branch out into the types of cuts (fillet, rib eye, striploin, ribs, flank, shoulder, leg, etc) and then finally into 3) the different levels of doneness for that type of cut together with a recipe on how to do / what to cook with it. This stuff is just general tidying up of the app and giving it richer content. It should not take you a lot of time to do. As for features, if you’re looking for ideas, look no further than your own advertising material for the Nano. Multi cook and multi step for starters. That’s basically what most people are asking for, together with support for other platforms (hence the popular request for the SDK, since your engineers can only do so much and we respect that).
This actually brings me to the reason I came back to this board to post this. The Nano. Your announcement (email circular that you sent out today) about the Nano… Seriously??? What is the point of that? I bet it was your finance guy(s) who came up with that product idea! We know why companies do that (for financial reasons since you sit on people’s money for a long time before you have to deliver anything). Here’s a free tip: when accounting and finance run the product path of a company, that’s when it starts going pear-shaped. Why am I annoyed at the nano you may ask? Well for starters, I am sure it will just heat up a bath of water exactly like the existing Anova unit… So what is the point of it really??? And two (this is the main reason) instead of focusing your efforts on producing ONE quality device from a hardware point of view (which you already have) with a top-class feature-rich app to run it, you’re gonna end up with two half-finished products and your 2.5 engineers are going to be overwhelmed. Wrong move! Even Apple limits their product range for that reason amongst others. Here’s the sad thing, I am having to use the app of a competitor of yours (I won’t mention their name here) to figure out what temperature to cook my food at because your app is sooooo lacking and poorly laid out. Unfortunately they don’t do 220-240v devices yet… but they’re working on one. This gives you from now until your competition get their 220-240v model out to sort out your app and/or release the SDK.
I have never loved and hated something at the same time as much as this device. Amazing hardware (which begs the question why the nano?) paired with half-finished software and questionable intentions on where the management’s focus is (finish the existing product or selling a new one which does what the first one should have done in the first place!). It is such a shame, but it’s not late. You guys need to have a serious management meeting to decide where you want to go with this. We’re with you and wish you all the best… but don’t take us for granted.
PS: Pls don’t come back to me with the argument that the Nano is cheaper therefore making it affordable to more people. 100 bucks vs 200 bucks on a sous vide unit that should last for years and years isn’t a big deal for people using it with iPhones or Androids costing much more than that and lasting two/three years tops.
Sorry for the long post.
