My first VR experience was using an early developer edition of Oculus Rift. It was easy to see the potential in the technology but it was somewhat overshadowed by the overwhelming feeling of motion sickness and the desire to throw up. My second experience was at Websummit in Dublin where I got to try the production ready version of Oculus Rift together with the hand controls. I was blown away by the experience. The problems with motion sickness had all but disappeared and the immersive experience and quality of content had improved immensely. Hand controls and spatial awareness sensors has helped to improve the perception of reality.
Since then we have acquired our own VR headsets and are like many media companies trying to figure out how to storytell through this new medium. The reality is that the technology is very much in the ‘early adopters’ phase of its lifecycle. Truly immersive VR headsets and the computers needed to power them are currently too expensive for the majority of people, the hardware and software needed to create quality content for these devices is also lacking or too expensive. Since these devices are largely stationary and located in your house the barrier for consumption is substantial, you have to be at home and it takes effort to put them on and find the content you want to consume. For a pretty comprehensive guide to the hardware and software currently available check out the guardians article, The complete guide to virtual reality – everything you need to get started
To deliver a truly personalised experience across multiple devices we require our users to login. To get our users to login we need to create a seamless login experience. Users often forget their username or password or do not understand that they can use the same login credentials between the different products or services we offer.
Password management services make it easy for users to keep track of their login credentials and use them across multiple platforms.
Apple and Google have created services to manage user credentials. Apples initiative is called “shared web credentials” and Googles “Google smart lock for passwords”.
If you update your apps and website to support both ‘shared web credentials’ and ‘Google Smart lock for passwords’ you can simplify the login experience for those users who have chosen to save their credentials with Apple and Google. The biggest benefit is in sharing login credentials between your website and your apps.
A couple of weeks ago, this article by Radosław Piekarz got some tracktion on /r/androiddev. While I am a fan of RxJava myself we use it extensively in our apps at VG.no, I feel this example was not the best use case for it. As others point out in the comment field, this can easily be solved without RxJava. Here is how:
Apps are evolving to be more than just functionality available behind an app icon on a users home screen. Custom keyboards, widgets, notifications, 3D touch, extensions and siri integration are among the many ways developers can now engage with users outside the confines of the traditional smartphone app on the homescreen.
On a cold Thursday in December, we held our annual Hack Day on the top floor of the VG building in Oslo. 30+ eager developers, designers and product people huddled together in front of the fireplace, to experiment, create and have fun with VG’s products and technology.
Surrounded by soda cans and bags of snacks, and entangled in wires of all kinds, we sat for 18 hours, churning out lines of magical code and golden pixels. Continue reading to see some of the things we did.
New functionality available in the next version of both Apple and Googles mobile operating systems (iOS9 and Android M) will have dramatic consequences for publishers trying to get users to use their apps instead of the mobile web browser. The next version of the iOS and Android operating systems will take deep linking to a new level.
Both Apple and Google have worked simultaneously on improving app linking, and essentially blurring the lines between content displayed in an app and content in a mobile website.
The Model-View-Presenter-pattern (MVP) has been the dominating trend lately when it comes the UI-layer architecture of Android applications. Frameworks like Ted Mosby, Nucleus and Mortar have all talked about Presenters to help you achieving a clean architecture of your app. They also (to a varying degree) help you with the infamous issues of device rotation and state persistence on the Android platform. This isn’t directly related to the concept of MVP, but the pattern helps you isolate the boiler plate code.
At VG we have been experimenting with offering location based advertisements in our VG app.
The goal is to deliver relevant advertisements to the the users at the right time and in the right place. Smartphones have provided the opportunity to serve more relevant information based on a users current physical location or locations they have previously visited.