GM’s 2024 Software Cuts: Mobile’s New Role

Listen to this article · 10 min listen

Key Takeaways

  • GM’s 2024 software cuts show they’re banking on in-house development, making mobile integration the main battlefield for keeping users engaged and staying ahead of rivals.
  • Building a solid automotive mobile app is a process that has to start with detailed user story mapping and finish with CI/CD pipelines so you can iterate quickly.
  • Proper mobile integration into vehicles relies on platforms like Android Automotive OS and Apple CarPlay, which help create a consistent and secure experience across devices.
  • You have to use secure data exchange protocols, like encrypted MQTT and secure RESTful APIs, to protect sensitive vehicle and user information.
  • Constant performance monitoring and paying close attention to user feedback are the only ways to refine the mobile experience, fix bottlenecks, and keep up with what consumers want.

When General Motors announced its big tech budget recalibration for 2024, it was more than just a cost-cutting measure. It was a clear signal about where the industry is putting its chips: on efficiency and a deep focus on core software competencies. This move shows just how much automotive mobile platforms are shaping the user experience. Mobile apps are now central to how drivers use their cars, manage services, and get information, which has a direct line to brand loyalty and recurring revenue. The real question is just how deeply integrated and functional these mobile experiences are going to get.

1. Define the Mobile-First Automotive Experience

Before you write a single line of code, you have to define the mobile-first automotive experience. This is about completely reimagining car interactions for a mobile context, not just slapping existing in-car features onto a phone screen. What can a smartphone actually add to the ownership journey? Start with deep user research to find the real pain points and wants of current vehicle owners. For instance, a 2025 J.D. Power study found 68% of new vehicle owners now expect remote control features through a mobile app, way up from 55% in 2022. This is the kind of data that should build your feature set. I always insist on starting with a complete user story map to chart every single interaction a user could have with the app, from the first time they research a car to managing service appointments years later.

Pro Tip: Concentrate on use cases that actually get better because of a phone’s portability and constant connection. Think pre-conditioning the cabin on a hot day before you get in, checking an EV’s charging status from your couch, or scheduling a service appointment in a few taps. Don’t just try to copy every button from the dashboard onto a smaller screen. That’s a surefire way to build a cluttered, frustrating app.

2. Architect for Scalability and Security

A strong, scalable, and secure architecture is the bedrock of any automotive mobile strategy. Because you’re dealing with sensitive vehicle data and personal information, security must be designed in from the very beginning. I’d start with a microservices-based backend that can handle millions of simultaneous connections, which is a realistic scenario for any major automaker. Using cloud-native platforms like Amazon Web Services (AWS) or Microsoft Azure gives you the elasticity and global reach you’ll need. For data exchange, you have to use secure communication protocols. For example, MQTT (Message Queuing Telemetry Transport) over TLS is great for the low-bandwidth, high-latency situations common in vehicle-to-cloud comms, as it keeps messages encrypted end-to-end. Your authentication has to be based on standards like OAuth 2.0 with multi-factor authentication (MFA) to keep user accounts locked down.

Common Mistakes: Forgetting about network edge cases. Cars drive through areas with spotty or no cell service all the time. Your app has to handle this gracefully, with offline features where it makes sense and clear communication to the user about their connection status. Another big misstep is failing to get regular, independent security audits. A 2024 Synopsys report (Source) found that automotive apps frequently have critical vulnerabilities because security testing wasn’t a priority throughout the development cycle. For more on this, you can check out some reading on securing mobile data in 2026.

Feature Native Development (Android/iOS) Cross-Platform Frameworks (Flutter/React Native) Android Automotive OS / Apple CarPlay
Performance & Responsiveness ✓ Unparalleled performance, responsive interfaces Partial (Good for less critical sections) ✓ Consistent user experience
Access to Device Hardware ✓ Full access to device-specific hardware ✗ Limited direct hardware access ✓ Integrated with vehicle hardware
Development Velocity ✗ Slower, separate codebases ✓ Significantly reduced development time Partial (Specific integration work)
Best Use Cases ✓ Core vehicle control, data display ✓ News feeds, loyalty programs ✓ In-vehicle infotainment systems
Security Considerations ✓ Can implement strong security Partial (Framework-dependent) ✓ Secure data exchange protocols
User Experience Consistency Partial (Platform-specific UIs) Partial (Can be consistent across platforms) ✓ Consistent across devices and vehicle models
Cost Efficiency ✗ Higher due to separate development ✓ Reduced development cost Partial (Integration costs)

3. Choose the Right Mobile Development Frameworks

Your choice of mobile development frameworks will directly affect your team’s speed, the app’s performance, and how easy it is to maintain long-term. In the automotive space, a hybrid approach usually works best. For the core features, vehicle controls, critical data display, native development for Android and iOS is still the way to go, since it gives you the best performance and direct access to device hardware. Use Kotlin for Android and Swift for iOS to build those high-performance parts. For the less critical, content-heavy sections of your app like news feeds, loyalty programs, or vehicle info pages, you can use cross-platform frameworks like Flutter or React Native. This can seriously cut down your development time and cost.

When it comes to the in-car infotainment systems, things are changing fast. Proprietary systems are still around, but platforms like Android Automotive OS (which is a full OS in the car, not the phone-projection Android Auto) and integrated Apple CarPlay are taking over. When you design your companion app, you have to plan for deep integration with these systems. That means using their APIs for smooth handoffs, sharing preferences, and keeping the user experience consistent. For example, if a user starts working through on their phone, that route should appear on the car’s main screen the moment they get in.

4. Implement Strong API Integrations

The mobile app is really just a window to the vehicle’s many systems and external services, which makes strong API integrations absolutely necessary. You’ll need to connect to the car’s telematics unit for real-time data like fuel levels, tire pressure, and diagnostic codes, and these APIs have to be both secure and efficient. I’d implement RESTful APIs for most data requests, with proper versioning to avoid breaking things, and use WebSockets for real-time updates like tracking the car’s location or getting instant alerts. You also have to think beyond the vehicle and integrate with third-party services for things like payment gateways, better mapping, or even smart home controls. Every single one of these integration points is a potential security risk, so rigorous API security testing, including pen testing and fuzzing, is not optional. I’ve personally seen a poorly secured third-party API compromise an entire system.

Pro Tip: Standardize your API documentation with a tool like Swagger (OpenAPI Specification). When the documentation is clear and complete, it cuts down on integration mistakes and helps both your internal teams and any external partners get up to speed much faster.

5. Establish a Continuous Integration/Continuous Deployment (CI/CD) Pipeline

Agility is everything in software, and that’s especially true for mobile apps where user expectations change overnight. You need a solid CI/CD pipeline to automate your build, test, and deployment work. Tools like Jenkins, CircleCI, or GitHub Actions can handle the orchestration. Every time a developer commits code, the pipeline should automatically run unit tests, integration tests, and UI tests across a suite of emulators and real devices. Automated security scans have to be part of this process too. Once all the tests pass, the pipeline builds the release candidate and, after a quick manual check, can deploy it to the app stores. This is how you push frequent updates and bug fixes to keep the app fresh and competitive. You can read more about reducing downtime with operational app launches.

Common Mistakes: Relying on manual QA. It’s too slow, too prone to human error, and just doesn’t scale for modern mobile apps. Another huge mistake is not having a bulletproof rollback strategy. If a new release ships with a critical bug, you must be able to revert to the previous stable version immediately without causing a major outage for your users.

6. Prioritize User Feedback and Iteration

Shipping the app is just the beginning. From that point on, mobile automotive software needs constant monitoring, feedback, and iteration. You need analytics tools like Google Analytics for Firebase or Microsoft App Center to see how people are actually using the app, which features they ignore, and where it’s crashing. You should also build in-app feedback tools so users can easily report bugs or suggest improvements. For new features or UI changes, run A/B tests to see what actually works best with your audience instead of just guessing in a meeting room. The automotive industry, which has historically been slow to change, has to get comfortable with the rapid iteration cycle that’s normal in consumer tech. Listening to your user base and responding with quick updates is the only way to maintain a mobile app that people find valuable. This all ties into managing your mobile tech debt and observability.

Building a compelling automotive mobile experience comes down to having a clear vision, executing the technical details carefully, and committing to never-ending improvement. By focusing on what users actually need and using agile development practices, automakers can earn their place in a fast-changing digital field.

What is Android Automotive OS and how does it differ from Android Auto?

Android Automotive OS is a full operating system built directly into the car’s hardware, running apps natively without needing a phone. Android Auto is different. It’s a projection system that simply mirrors a limited set of apps from your connected Android phone onto the car’s display.

Why is security particularly important for automotive mobile applications?

These apps handle extremely sensitive data: your real-time location, personal driving habits, payment info, and even remote controls for locks and engine start. A security failure isn’t just a data breach. It could lead to car theft or physical danger, which is why strong encryption, authentication, and frequent security audits are non-negotiable.

What are the benefits of using a microservices architecture for automotive software?

A microservices architecture means breaking a big application into smaller, independently running services. This makes the system more scalable because you can scale up individual parts as needed. It’s also more resilient, since one failing service won’t bring down the entire app, and it lets development teams work faster and more independently.

How can automakers ensure a consistent user experience between the mobile app and the in-car system?

You get consistency by creating a shared design system, using common APIs for data, and designing smooth handoffs between the app and the car. When you start navigation on your phone and it smoothly appears on the car’s screen, that’s good integration. Platforms like Android Automotive OS and Apple CarPlay provide frameworks that make this much easier to achieve.

What role do real-time data protocols like MQTT play in automotive mobile connectivity?

MQTT is a lightweight messaging protocol that’s perfect for the often-unreliable networks that cars connect to. It allows for efficient, real-time data flow between the car and your app for things like status updates, diagnostic alerts, or remote commands, all while using minimal data and battery power.

Editorial Team

The Editorial Team at Mobile Product Studio is a group of writers and editors who cover technology, products, and how teams ship. They research each story and publish under a shared desk byline — experts in their fields, working as one team.