Well, I appreciate that the cloud storage solution is the reason the phone exists, but, honestly I fully believe it's an objectively inferior solution compared to an SD slot - though it could freely exist alongside an SD slot, and I suspect much of the code for choosing what to back up might be useful for optimizing which data to migrate over to SD. And having the cloud solution in addition to the local storage and SD would be fine too - but the user experience of having to wait say, 5 minutes for the app you wanted to launch to download, because your phone decided you don't need it that bad and you've got a mediocre signal, represents a use flaw that simply wouldn't exist on one of my phones with an SD slot, where the full 16/32/whatever internal storage can be fully dedicated apps, and I can use the SD card for my large piles of media. I tried to use the cloud storage for the first two weeks or so, purposefully keeping the device pretty packed, and what ends up happening is that I don't use my phone for ancillary tasks as much - when you go to take out your phone to launch a lesser used app that's situational - like the eBay app, when I had to get an address to ship something, it's not ready to go. And that wait meant that I simply used the browser instead, completely negating the reason I had the app in the first place, which harms the user experience compared to a normal android device. And sure, you could pin the apps so they don't upload, but then it focuses more on shoving pictures up, which in my case saves less space since I have relatively few, and also could hurt the user experience in the event of a slow/no connection - "Hey, look at this picture of my dog. Err, hang on, it's loading... ...Nevermind, I'll send it later"
Further, the nextbit cloud lacks utility compared to some other cloud programs, all of which have solid android apps. If I want my pictures to go online, onedrive, dropbox, google drive, and at least 10 others can all do that seamlessly - and in the case of onedrive, which I use, automatically put that content on all my phones, desktops, all nearly instantly. With the nextbit cloud, there's no such syncing - sure you can use the web client, but it can't sync my pictures over to my mac, windows phone, iphone, and such. The app backup is neat, and novel for android, but not that useful. And the Nextbit cloud won't do other media too, so I can't say, put some music or movies up there and stream it to myself, which I can with onedrive, and several others. Plus, pardon my frankness, but I trust google/microsoft/dropbox uptime more than nextbit - you guys haven't had a big outage yet or anything that I know of, but what happens if nextbit fails? Is my cloud content gone? That's a worry I don't have with microsoft/google, since they aren't gonna disappear anytime soon, and more importantly they allow me to nearly immediately have a local copy on nearly every device I have - so even if microsoft went bankrupt, my house burned down, and I got struck by lightning, killing my phone, all in the same day, I'd still have a copy of my media and stuff on my work computer, my car, and such. (Of course, I hope very strongly nextbit doesn't fail, because we need more people making phones that aren't just boring slabs of glass and grey aluminum, but it's certainly more likely than losing a tech giant.)
Now, obviously having the device almost full is a worst case scenario, but it's the scenario you guys seem to target, since, surely, if I have say, 20gb free, there's no reason at all to back anything up - I would hope that only when the phone is within a couple gigs of full, does it start seriously migrating things to cloud storage. And as soon as it does, an SD makes more sense - or, you know, actually including a fair bit of storage from the factory - 128gb of eMMC is like $25, and I have to assume, less in quantity purchases. UFS-II in the same 128gb is more like $50. Either way, that's DRAMATICALLY less expensive than the literally hundreds that the likes of apple and samsung like to charge for storage upgrades. You really wanna disrupt the market and make an interesting phone? Don't make a mediocre cloud service - make sub $400 phone that has flagship specs, looks as sexy as the Robin currently does, but has 128gb of memory standard, with an SD slot to boot - that would be truly disruptive. Though I'd absolutely settle for just 32gb + SD, as 32gb is enough for most users, and people like me can add as much storage as they feel they need.
With regard to the launcher, yeah, I don't mind that the nextbit launcher exists - I'll just never use it personally. And, as you say, that's the best thing about android.
Certainly your OS updates are solid - no July Security update yet - but you're kicking most of my other phone's butt. I'm looking forward to that Q4 battery life update.
As for the 2gb of RAM vs 3gb, I'm sure there's use cases where it makes a difference, but in my experience, it doesn't. I don't have a Nexus 5x anymore - sold it before I got the Robin, so I haven't had a chance to directly compare them. But I never felt like it was choppy or slow or anything - never really went above 1.9gb used (quick check shows my robin is at 2.0gb used right this second), and the background app culling and such didn't really seem any worse. But I heavily use 4-5 apps, rather than 20 or something, so maybe it just doesn't show for me. Individual users will need to decide for themselves, I guess - but for me, 2gb or 3gb just doesn't matter.