Republicii Street, No. 9, TM, Romania +40-256-201279
Tech

Rolled out in 2014, Android Auto now features widespread integration in cars from major brands. As Digital Trends recently put it (October 2018): “becoming the dominant operating system in cars has long been an ambition for Google, and Android Auto, launched in 2014, represents the tech giant’s first step toward that goal”.

It may seem like four years of (apparently) slow progress have reduced the glow of Android Auto. But in fact the auto market in itself is much slower than the smartphone market, for example. Android Auto has matured to the point where the list of car manufacturers whose systems integrate Android Auto is now very exhaustive.

Check out a list of all the cars with Android Auto from Digital Trends here (dating August 2018).

Here you have an October 2018 similar list.

 

With an ever-growing list of partners, Android Auto is set to become the top car infotainment system

 

Those of you already familiarized with digital auto systems already know about the dominance-to-be of Android Auto. One may say Google is not yet fully there. However, expanding both the development options for this operating system, as well as its incorporated features is an ongoing thing.

For those who are still uncertain about the benefits of building your app for Android Auto, here you will find a comprehensive Pocket Lint article on Android Auto.

Now you have Google Assistant in your car. We will also witness the first car to come with Android Automotive out of the factory, as Volvo has now confirmed its all-electric Polestar 2 as the first car to run Android Automotive. Car manufacturers that used to be Android-free have sensed the shift in the market and will provide Android Auto integration in some of their future models.

 

Making an app Android-compatible is a key success factor

 

Apps follow users around, and the digital car systems have translated this modern trend into infotainment apps. Voice controlled, serving our various needs or whims, seamlessly integrated… These apps might even surpass what happens now with smartphone-only apps in terms of usage and importance. With the perspectives opened up by driverless cars, new possibilities unravel. And obviously Google wants to be on top of this game.

Making your apps (new or previously build for a different OS) Android Auto–compatible means allowing them to have a successful future.

Remember that Android Auto “enables you to extend your app to work with in-vehicle console systems running Android Auto. These systems provide a simplified interface for apps that can be used in a car, allowing users to take your app with them on the way to the grocery store or on a long road trip.

Apps that work with Android Auto consoles run on a connected device, such as a phone or tablet. The app communicates via specific APIs with the in-dash console, which provides a user interface for the connected app that is designed for use in a car”.

 

We bring you the power to extend your Android app to support use in vehicles!

At LASTING Software we are experienced in various hardware configurations, device types and deployment environments. We proudy put this know-how at your disposal.

With what we mentioned above, as well as the news about the world’s largest automobile partnership/alliance, aka Nissan, Mitsubishi and Renault partnering with Google to use the Android operating system in their cars starting in 2021, your apps really need to be able to integrate the Android-powered infotainment space as soon as possible.

LASTING Software provides experienced Android application development services

Our in-house teams of software engineers specialize in the following:

– Platforms: Mobile, Wear (Watch), TV, Things (IoT) and Automotive

– Programming languages: Kotlin and Java

*Moreover, our innovative LASTING Software team also crafts apps that function in both the Android and iOS environments. We use Flutter – Google’s mobile app SDK. For those use cases that are less sophisticated and suitable for this approach, the client can benefit from a faster and more cost saving development process.

Do you have an Android app you want developed, optimized, and monetized? Nowadays, with the Google products widely used across industries, any company that activates into web or mobile services needs to build its own reliable and versatile Android applications, as part of its market presence.

Keep ahead of your competition by partnering with LASTING Software!

0

Tech

Code reviews are part of any software development environment. Not the most pleasant part, in what a developer is concerned, since it involves his/her work being scrutinized and it may feel stressful, “but it’s also one of the best ways to get feedback on your code, to catch typos and mistakes, and, more broadly, to grow as an engineer”.

In order to take some unnecessary pressure out of this process, there are tips & tricks synthesized in the online media that help both code developers and code reviewers make the best out of this stage. We asked a few collegues here at LASTING Software to help us select a few best practices/rules/recommendations.

Let’s review some of them, starting with the most quantifiable ones.

 

5 practical rules for code review

 

A developer should review less than 400 lines of code at once;

Keep the inspection rate at a density of less than 500 LOC per hour;

Try not to surpass 60 minutes at once without taking a break, if you want to keep a high performance;

Establish tangible, measurable goals for the entire process;

Use code review procedures that can be followed and tracked (checklists, collaborative tools, fixing processes to be implemented).

(Selected from Best Practices for Code Review, as presented by SmartBear)

 

5 recommendations for developers

 

Prepare a quick summary where you explain the problem and the proposed resolution;

Auto-review, prior to someone else reviewing your code, so you can trim some of the problems yourself;

Communicate – by using annotations to highlight all the soft spots, and tag the right people involved in the project that might clarify these problems you feel you need a second opinion about;

When the reviews are back, remember the importance of team work and concern yourself with their utility and processing prior (and over) feeling anxious;

Refactor changes without altering behavior.

 

5 recommendations for code reviewers

Always keep in mind the code purpose and the project scope;

Ask clear questions whenever the functions and classes reason does not reveal itself;

Be clear when highlighting the problem you have identified, and propose alternative solutions;

Write the reviews in a neutral and concise manner and avoid absolute judgments;

Don’t forget to mention the good things you notice – keeping it clear you review with the overall quality in mind, not just to hunt the errors.


You may find more useful advice, examples, and technical guidelines related to code reviewing in our third source of inspiration for this article – on Medium.

 

0