Perhaps you should do a bit more reading on these tools. With life experience you will learn that these tools really help you get your work done, and right now you're likely solving what they have already solved for you. Rails is a highly modular architecture with some sane implementations by default, but I promise you there are many pluggable pieces that exist that do just about everything you could ever dream of.
I don't like the suggestion that if I don't care for rails I must be using it wrong. I have worked with many technologies over the years and I know which ones I like and which ones I don't.
I suspect it is an issue of preference. I am sure it is possible to be productive using Rails, but the interface style and overall structure is a bit heavy handed for my taste. I prefer tools which stay out of my way and I'm not terribly fond of working inside an "ecosystem".
What's there to reverse? CarPlay is extremely basic, you send a surface geometry to the iPhone and you tell it what it can be used for, a lot like Apple Watch complications, and then CarPlay can decide what to send to the buffer.
Example:
In a Mini, with wireless CarPlay
I get a Main View for CarPlay's springboard, and configurable split screen for other car functions, however one of the functions is a media view for currently playing media. This allows me to use any car functions in the main view and still see what media is playing from any source including CarPlay, and it shows the Album View from CarPlay.
The (MFi?) authentication prevents you from making your own carpc compatible with carplay because of encryption, there are efforts to break it (extract key) but AFAIK none of the public ones have succeeded so far
