I thought I would share my new user experience. Not in any way critical of what has been done. More as end user feedback to product managers.
I ordered a Nextcloud Box on Thursday, and a Pi 3 B for a variety of reasons, including getting away from Dropbox.
What made me press the order button was that it was made by Western Digital, it was low cost, the documentation said it worked with the Pi 3 and was based on Ubuntu Core. All good things.
It arrived on Monday (WD logistics are good in Europe) and I had no problems assembling it using the tool provided.
Inside the box was an SD Card and a little paper label which says ‘For Raspberry Pi 2 only’.
I was a bit disappointed as the nextcloud box website and forums including this post talk about an April 2017 release to manufacturing and it is now July 2017. Anyhow I flashed an SD with image for the Pi 3. (Not all that easy, required an Ubuntu Laptop with an SD Card slot and forum searching - I would say this is an intermediate system admin task).
I rebooted, with a USB keyboard, HDMI Monitor connected and the device came up. I went through the installer and instructions but something odd happened in setting up my Ubuntu One Login SSH keys and try as I might I was unable to ssh to the box. It turns out my ssh key was corrupted but still accepted by Ubuntu One and once set by the Nextcloud box could not be adjusted.
I flashed the SD card again, and this time created a brand new user account on my Ubuntu Laptop and a brand new SSH key which I then set as the key with Ubuntu One. I would say that this activity was of an ‘advanced’ system admin level. I am still unsure how to grant SSH access to another user, or from my Mac for example.
I could not however login. SSH said the device said it was shutting down. There was no such indication on the console. A good few minutes later it did indeed shut down with the usual visible prompt on the console. Once rebooted SSH finally came to life. This was confusing for me although based on intuition I decided to wait and see if the device would reboot when it looked like SSH was not working. I dont know that many end-users would have.
I installed Lets Encrypt and now find there are various things I am unable to install as they are incompatible with Lets Encrypt. This is a shame because I must use certificates and https as a matter of best practice. Installing Lets Encrypt required SSH access - it would be better in the Web UI Admin.
I am not clear at all how the box keeps up to date, and whether and when the Lets Encrypt certificates will renew. Something to learn.
Finally I was able to set up users and finish the GUI setup in the web browser and this was easy and well thought out although getting email alerts working will prove to be a challenge for me as usual because SMTP relays. I thought this was beginner level system admin and it was easy enough to accomplish.
Overall. The out of box experience seems pretty daunting for a new user. I would suggest you consider getting WD or other hardware partners to provide a complete tested solution rather than a self assembly kit. I spent a good part of a day on it which is not all that economical for my time although I wanted to learn more about Ubuntu Core so theres that.
Overall though it is a good product idea. I will now test it out in my environment over a period of time and am hoping its a keeper.