Showing posts with label HTML5. Show all posts
Showing posts with label HTML5. Show all posts

What are the 5 all-time most popular QNX videos?

Geez, I thought you'd never ask. Seriously, the question came to mind earlier this week, so I decided to find out. A quick trip to the QNX YouTube channel provided the answer.

What that trip didn't tell me is why these videos are the most popular. I can think of several reasons, but the most obvious is that the videos all hint at a future in which driving is more connected, more convenient, more enjoyable — and also a little safer. But don't take my word for it. Check out the videos, if you haven't already, and judge for yourself.

Without further ado, here are the top five, along with my favorite scene from each one.

#1
First up, at more than 525,000 views, is Imagined: Your car in the not-so-distant future. Best part: the augmented reality-enhanced stop sign (1:10).



#2
Next, at more than 230,000 views, is QNX seamless connectivity. Best part: John Wall speaking on the real challenge of making a connected car (:50).



#3
Close behind #2, at more than 213,000 views, is The QNX secret to making hands-free noise-free. Best part: The marching band (1:21).



#4
Next, at more than 85,000 views, is QNX HTML5 series - Interview with Pandora's Tom Conrad. Best part: It's all good, but I love the bloopers (3:00).



#5
And last, at more than 34,000 views, is QNX technology concept car - Bentley Continental. Best part: the couches.



One that didn't make it...
And, finally, here's my current favorite. It's not one of the top five... yet. But I think it should be:



Prefer your whitepapers in German? Have I got a link for you

Germany has long been a strong market for QNX technology, particularly in the industrial, medical, and automotive sectors. Consider, for example, the many cars from Audi, BMW, Mercedes, and Porsche that ship with QNX technology on board.

It's no surprise, then, we've been redoubling our efforts to publish our latest technical whitepapers in German. So if you sprechen sie Deutsch (I hope I said that right) better than you speak English, I invite you to visit the German section of our whitepapers page.

Papers include:

  • Wann genau benötigt man ein Echtzeitbetriebssystem?
  • Funktionale Sicherheit komplexer Software-Systeme – Teil 1
  • HTML5 – die Zukunft des In-Car Infotainment?

    For the full list of papers, click here.

  • Using Crank Storyboard to create an automotive user interface

    Just how adept is the QNX CAR application platform at supporting a variety of user interface technologies and toolkits?

    From the beginning, we've promoted flexibility as a key quality of the QNX CAR application platform. For instance, the platform lets you work with a variety of user interface technologies, including HTML5, Qt, OpenGL ES, and others. What's more, it lets you blend UI components built with different technologies on the same display, at the same time. You're not forced into using a single API or toolkit.

    When it came time to build our new technology concept car, we decided to put this flexibility to the test. After all, the whole point of the concept car is to demonstrate the capabilities of the QNX CAR platform. So, for the first time, we tried building a user interface with the Storyboard Suite from Crank Software.

    How well did the QNX CAR platform and Storyboard work together? I think the results speak for themselves. For instance:



    Of course, this photo can't demonstrate the smooth animations and snappy performance of the car's user interface. For that, I recommend one of the videos shot at CES, including the excellent video from TI.

    So why did we choose Storyboard? For one thing, it allowed our concept team to take UI components created in Photoshop and import them directly into their live design. Rather than spend days or weeks recreating the UI in code, the team's engineers were able to start with what the UI designer provided. Which made prototyping and fine-tuning the UI a lot easier.

    Mind you, that wasn't the only reason the team used StoryBoard. But instead of listening to me blather about it, check out this video:



    Key takeaway: If you're building a UI for your QNX-based system, you owe it to yourself to check out Crank's Storyboard Suite. You can learn more on the Crank website.

    QNX at SAE Convergence: Cool screens and a mobile theme

    Let's start with the theme. And no, I don't mean the kind of theme you download onto your smartphone. I'm referring instead to the main theme of a press release that QNX issued yesterday at SAE Convergence.

    First, some context. If you're an automaker, you have little choice: you have to offer infotainment systems that can keep pace with the crazy fast advances in mobile devices. You also need to keep your systems fresh with apps, features, and content that consumers will expect long after they've bought your car. And to do that, you'll need to tap into the skills and products of the mobile app community. Otherwise, that ultra-cool infotainment system you ship today will rapidly transform itself into the 8-track of tomorrow. Goodbye, brand image.

    The QNX CAR 2 application platform, with its solid grounding in HTML5, is designed to help infotainment-system designers conquer these (admittedly difficult) challenges. HTML5, after all, has become the lingua franca of the mobile apps market and offers an ideal bridge between the mobile and automotive worlds.

    One thing was missing, though — a toolkit that would make it easy for mobile app developers to target the QNX CAR 2 platform. Yesterday, at SAE Convergence, QNX announced a new HTML5 SDK designed to do just that.

    An SDK for (auto)mobile developers
    The HTML5 SDK for the QNX CAR 2 platform is an extension of the open source BlackBerry WebWorks framework, specially optimized for automotive environments. It allows developers to write, test, and package feature-rich automotive apps based on HTML5, CSS3, JavaScript, and other open standards. It also provides the missing glue between high-level apps and the car, through specialized APIs that provide access to automotive devices and hardware.

    Runtime emulator for quicker testing and debugging
    This is where the first of the screens comes in. To speed development, the HTML5 SDK provides an emulator that lets developers quickly see how their apps would look and function in a car. Developers can use the emulator to perform JavaScript debugging, HTML DOM inspection, automated testing, and screen-resolution emulation, all from the convenience of a web browser. They can even make changes to their apps and view the results without having to recompile. The simulator is based on the open source BlackBerry Ripple emulator, used by thousands of mobile developers.

    For instance, in this screen capture, the emulator is being used to test the virtual mechanic provided by the QNX CAR 2 platform:


    Click to magnify

    Here's another example, where the emulator is being used to test an audio control application. If you were running this emulator session, you could manipulate the app's onscreen controls to adjust volume, bass, treble, fade, and balance; you could also observe the changes to the underlying data values in the right-hand panel. And you could work the other way: by changing the controls on the right, you could observe changes to the app.


    Click to magnify.

    QNX also plans to create a virtual marketplace that will allow developers to make their QNX CAR 2 applications available to automakers. The marketplace will provide common ground for app developers and automakers to work together, and will allow automakers to preview the applications that best fit their brands and satisfy their customers. The marketplace is expected to go live when the HTML5 SDK is released.

    By the way, my colleague Kerry Johnson provides an interesting back story to the SDK, including the kinds of APIs it provides. You can read his post here. You can also find more images of the emulator on the QNX Flickr page.

    3D navigation from Elektrobit
    Now for the other screens. Besides announcing the SDK, QNX has brought its QNX reference vehicle, a modded Jeep Wrangler, to the SAE show floor. As always, the Jeep is running the QNX CAR 2 platform. But this time, the Jeep also includes a cool 3D navigation app from automotive software vendor Elektrobit. Here are two examples of the Elektrobit app:





    That's it for now. But before you go, be sure to follow @QNX_Auto on Twitter, where we are covering the latest developments, both QNX and non-QNX, from SAE Convergence.

    What has the QNX auto team been up to?

    Well, let's see...