5 ms·

God I wish BB10 was open sourced. Today the biggest problem with phones is their bloated runtimes, android being the largest offender. I want something with the

God I wish BB10 was open sourced. Today the biggest problem with phones is their bloated runtimes, android being the largest offender. I want something with the form factor of the q10 running a QNX-based os I can ssh to and use rsync to copy music, contacts, and a calendar to.

walterbell 6y ago
BB10 had the opportunity to support security and the open web, instead of chasing the app store quagmire. WebOS is now open-source and based on OpenEmbedded, which can be minimized. Blackberry has already ported some of their special sauce to Android, they could do the same for WebOS, extracting suitable components from both BB10 and QNX/automotive. Instead of worrying about apps (previous war), they could invest in a Rust-based browser and WebAssembly for mobile devices, building on their security strengths. Allow the 'mobile' device to dock with USB-C to a desktop display and keyboard, and you've got a WFH story for security-sensitive apps/data. They have enough proprietary security software to sell on top of WebOS. Convert Blackberry Messenger to IETF MLS (open-standard E2E encrypted group messaging) and enable interop with Matrix and other apps/platforms that embrace MLS, while (re)creating a business identity network. By focusing on open standards and honoring their heritage in email/chat and physical UX, they could provide a usable alternative for high-end users who favor productivity and security without lock-in. Yes, BB was once the king of carrier gardens, but Apple is now a garden to be escaped, not emulated. There may be Firefox browser engineers recently on the market, who can hit the ground running with variations of the above strategy. LG, lead developer of OSS WebOS, does not compete with QNX or Blackberry. QNX remains an undervalued gem. A hybrid OSS+proprietary model can bridge BB past & future, but it requires vision from Blackberry, not only a new brand licensee.
- 908B64B197 6y ago
  Truth is, the company should have abandoned it's OS before they released their first touch screen device and go with Android. I remember playing with it (the Storm?). It was 2 years after the iPhone was released and it was two years behind the original iPhone. The only moat to keep users they had was their messaging app, but Facebook Messenger and WhatsApp killed it with interop. And it's not like their userbase was as valuable as, let's say, Bloomberg chat.
  - rcfox 6y ago
    The first release of Android was only a couple months before the release of the Blackberry Storm. That obviously wasn't an option.
    - 908B64B197 6y ago
      I'm really getting downvoted without explanations here. The Storm should have been a warning sign that their OS was starting to heavily lag behind. By the time it arrived on the market Apple already had the App Store and the 3G on the market. Anyone from BlackBerry taking a trip to the local mall would have noticed what was wrong with the Storm and the OS in the first 30 seconds when trying a (first gen!) iPhone.
- protomyth 6y ago
  There developer story was way too confusing. Adobe Air just wasn't a good idea. Blackberry had been Java, and I wonder what made that a pain. The Runtime for Android was a good idea, but they really needed to pick something. QNX is doing fine in cars, shame it never really got a chance. The 2 screen Doom and rebooting drivers over the network showed some amazing stuff.
  - mightyscouse 6y ago
    It wasn't so much that it was Java (albeit ME without generics) it was more you didn't get an awful lot out the box. You had to hand roll all your UI with drawing routines that scaled across various devices and handle all the touch/tracker button events yourself. Networking was a minefield. Depending on your connection (bis/bes/tcp/WiFi) you'd have to pass various undocumented params. Think we had a modified version of some networking code a RIM employee has given us, God knows how you'd have figured it out as an indie dev. The support and open source ecosystem wasn't really there at the time either. Just a couple of devs who were super prolific and knowledgeable on the dev forums (thanks Peter Strange, if you're about HN)
Lorin 6y ago
Q10 was a great form factor... and BB10's swipe methodology and permission control were great. Sadly they couldn't compete with Android and were really headstrong. Give me a Q10 with a higher resolution display, better camera, USB C, and you got yourself a banger. Sadly the Key2 physically was a step back from the comfort of the KeyOne. I hope this device actually stacks up, or they finally decide to make an official physical keyboard attachment for some other popular devices

walterbell 6y ago

BB10 had the opportunity to support security and the open web, instead of chasing the app store quagmire. WebOS is now open-source and based on OpenEmbedded, which can be minimized. Blackberry has already ported some of their special sauce to Android, they could do the same for WebOS, extracting suitable components from both BB10 and QNX/automotive. Instead of worrying about apps (previous war), they could invest in a Rust-based browser and WebAssembly for mobile devices, building on their security strengths. Allow the 'mobile' device to dock with USB-C to a desktop display and keyboard, and you've got a WFH story for security-sensitive apps/data. They have enough proprietary security software to sell on top of WebOS. Convert Blackberry Messenger to IETF MLS (open-standard E2E encrypted group messaging) and enable interop with Matrix and other apps/platforms that embrace MLS, while (re)creating a business identity network. By focusing on open standards and honoring their heritage in email/chat and physical UX, they could provide a usable alternative for high-end users who favor productivity and security without lock-in. Yes, BB was once the king of carrier gardens, but Apple is now a garden to be escaped, not emulated. There may be Firefox browser engineers recently on the market, who can hit the ground running with variations of the above strategy. LG, lead developer of OSS WebOS, does not compete with QNX or Blackberry. QNX remains an undervalued gem. A hybrid OSS+proprietary model can bridge BB past & future, but it requires vision from Blackberry, not only a new brand licensee.

908B64B197 6y ago
Truth is, the company should have abandoned it's OS before they released their first touch screen device and go with Android. I remember playing with it (the Storm?). It was 2 years after the iPhone was released and it was two years behind the original iPhone. The only moat to keep users they had was their messaging app, but Facebook Messenger and WhatsApp killed it with interop. And it's not like their userbase was as valuable as, let's say, Bloomberg chat.
- rcfox 6y ago
  The first release of Android was only a couple months before the release of the Blackberry Storm. That obviously wasn't an option.
  - 908B64B197 6y ago
    I'm really getting downvoted without explanations here. The Storm should have been a warning sign that their OS was starting to heavily lag behind. By the time it arrived on the market Apple already had the App Store and the 3G on the market. Anyone from BlackBerry taking a trip to the local mall would have noticed what was wrong with the Storm and the OS in the first 30 seconds when trying a (first gen!) iPhone.
protomyth 6y ago
There developer story was way too confusing. Adobe Air just wasn't a good idea. Blackberry had been Java, and I wonder what made that a pain. The Runtime for Android was a good idea, but they really needed to pick something. QNX is doing fine in cars, shame it never really got a chance. The 2 screen Doom and rebooting drivers over the network showed some amazing stuff.
- mightyscouse 6y ago
  It wasn't so much that it was Java (albeit ME without generics) it was more you didn't get an awful lot out the box. You had to hand roll all your UI with drawing routines that scaled across various devices and handle all the touch/tracker button events yourself. Networking was a minefield. Depending on your connection (bis/bes/tcp/WiFi) you'd have to pass various undocumented params. Think we had a modified version of some networking code a RIM employee has given us, God knows how you'd have figured it out as an indie dev. The support and open source ecosystem wasn't really there at the time either. Just a couple of devs who were super prolific and knowledgeable on the dev forums (thanks Peter Strange, if you're about HN)

Lorin 6y ago

Q10 was a great form factor... and BB10's swipe methodology and permission control were great. Sadly they couldn't compete with Android and were really headstrong. Give me a Q10 with a higher resolution display, better camera, USB C, and you got yourself a banger. Sadly the Key2 physically was a step back from the comfort of the KeyOne. I hope this device actually stacks up, or they finally decide to make an official physical keyboard attachment for some other popular devices