Nextbit
nextbit.com
nextbit.com
> No barriers.
Robin comes with an unlocked SIM, so you can choose the right carrier for you. And because we think what you run should be up to you too, we’ve made it as easy as possible for you to customize Robin. Its unlocked bootloader and open source drivers make it easy to load CyanogenMod or any other ROM you want and Robin will still be under warranty.
I'm not up-to-date on my Android phones, but my impression is that this isn't particularly common. Most of the concerns I see on this thread are complaints about how secure it is to sync one's data on someone else's servers... but doesn't this make it much simpler to hack around with the phone and disable that functionality? (Or perhaps even set up syncing with one's own servers?)
Having an unlocked bootloader opens to the device up to far more security vulnerabilities should it fall into the wrong hands. In some cases attacks can be performed even if the device has full disk encryption[1].
[1]: https://www.fcc.gov/consumers/guides/cell-phone-unlocking-fa...
One annoying example is how Sony's Xperia phones can have their bootloaders unlocked, but Sony keeps the secret sauce behind their image sensor's software locked up in a proprietary, inaccessible blob that (IIRC) other ROM makers have been unable to integrate into their Xperia builds.
If Nexbit is not only unlocking the bootloader but providing the hw drivers as open source, that could be a bigger deal.
To be fair, Apple - the self-proclaimed mobile security champion - similarly claims to be concerned about security but does not[1] readily provide all that information (cipher suite, key management). The results after Googling "iPhone cipher suite" all point to non-apple domains.
Dry reading makes poor copy on any landing page, and most consumers will take the manufacturers word for it when they claim to be "secure".
I instantly stopped caring once I read this poetic marketing spiel.
Of course I know what this actually means: your phone is now an even dumber dumb terminal for accessing the cloud.
I personally gave up when I saw no references at all to encryption, security, or privacy. I assume this thing promiscuously mirrors everything unencrypted (at rest) to someone else's server, or if data is encrypted at rest it's done with someone else's key (server-side "encryption"). That's not only a privacy nightmare but also a security nightmare. What happens if I store a valuable credential, card number, etc. on my phone? Barrels of fun.
For example someone with access to this data could:
find /path-to-cache | grep id_rsa ...
... then see how many machines on the Internet they can ssh into using Android SSH client certificates. Blamo, instant botnet.
> It is securely transmitted and stored encrypted on our servers. And we provide two factor authentication with Google.
which could mean any number of things.
I thought they did a good job of giving very "real" answers too, they didn't seem to dodge any topics.
https://www.reddit.com/r/IAmA/comments/3l726c/we_are_nextbit...
2. (censored) swearing in marketing materials - Not classy. Or to put it the way nextbit's marketing would understand, F*ck no.
Come on people. Pretty designs are meaningless if you can't actually use them. How can I have faith in the claims you make about your phone if your website is this unusable? This exact form-over-function is why I hate the modern web.
More people need to see http://motherfuckingwebsite.com/ and understand.
PS: I logged in just to reply to your comment!
Still, no website but youtube in fullscreen has made my poor pc do these unspeakable things to its fan speeds
They are solving a non-existent problem which introduces real problems. I don't want to sync data on my mobile data plan. I want to have it on my phone.
It's great that they protect the data in transit and store it encrypted on their servers, but if the data is being encrypted by the server, and can be decrypted by the server, it's not really protected. Unfortunately, doing encryption at the server would allow them to make use of single instance storage and compression, which greatly reduces their data footprint and I'm guessing if the data was protected by the a client-owned key, they would have made mention of that along with their other security specifications since it is a big plus and would easily be a feature worth calling out.
I'm curious what else they have in the works that would take advantage of the complicated stack they've built from OS-level customizations on up that might present a more compelling reason to chose this product.
1. is it a full backup like titanium backup or is it adb backup thats not as good.
2. Some apps you can't just uninstall and reinstall without reverifying every time. Google authenticator is an example, that I don't think you can backup at all with adb or theres apps like line, that send you a txt message every time you reinstall even with titanium backup. How would Robin handle that ?
This would be far better as a minor benefit that Google built into Android directly. They did hint at remote virtualized apps a while back (in the context of "try before you buy") but nothing came of it.
I'm not sure anybody cares about what Nextbit has created here. From the comments on HN, I'd suggest they haven't identified the market need.
See: YotaPhone, YotaPhone2[0]
[1] https://www.kickstarter.com/projects/nextbit/robin-the-smart...
Well OK, I guess.
I wish I could play around with some of my performance settings to squeeze even just a little bit more battery savings in.
edit: it was actually a tablet
Android is really not great. It's just the best we have. It's weird to see projects like these, with a community-oriented and community-organized feel, that buy into Google's ecosystem so much.
Firefox OS couldn't attract WhatsApp to build an app because of lack of a user base, which put off many of their European customers who _only_ use WhatsApp for messaging. WhatsApp isn't the only example. Even Facebook was essentially just a webview. Convincing companies to spend the resources to get onto your platform is actually really hard, and usually means developers shell out cash to companies like Facebook and WhatsApp to get them to build for their OS. You end up with this vicious feedback loop that kills the platform.
Android already has an ecosystem with top-of-the-line apps. If you want to build your own mobile operating system, building on Android gives you an immediate advantage because you already have developers building for your product, which means real people in the real world actually have a reason to use your phone.
I don't even really use any third party apps but Google Maps, Gmail, Chrome, and Google Voice/Hangouts keep me on Android. At the time (and maybe now?) WP8 didn't even have proper notifications and IE had issues rendering random websites which was annoying.
There certainly were many things Microsoft did better though, like their keyboard, copy paste, and the speed of the UI. It's too bad they seem to have given up on it.
Google was able to say "Ok, we want to add support for X thing into our OS, so rather than leave it there doing nothing lets build a phone around that feature".
Buy Motorola was the smartest push google has done in years. It gave them patents, manpower, and the ability to bring ANY technology they wanted to an at least small scale high quality production run.
I know a few people that are looking to upgrade from the one plus one, but have no options due to lack of NFC on other one plus models. This seems a great choice for them.
It is a cool and convenient feature, it stops the causal girlfriend/boyfriend that tries to spy on their partner but not much more.