Official Feature Request Thread

[NoTec]

You've all seen this thread before, but I am going to beat a dead horse and ask you guys again, because we are seriously building this program for YOU guys, and we really want it to be as full featured as possible.

What realistic features are you guys looking for in a new mobile media center? What type of integration and hardware compatibility are other programs missing? Is your main focus speed? Looks? Interface logistics? Customization? Do you want everything to be in one program or have addons/modules with the features you want?

List them all here! We need your feedback to make this the ultimate CarPC application.

[executor485]

I'll chime in my biggest concerns and we can roll from there
1) I've been waiting for a GOOD bluetooth support for phones, nothing so far has worked well for windows mobile phones especially on CDMA. - realistic, maybe not, but thats a huge want for me and others I'm sure.
2) The ability to use iGuidance, map monkey, map point, etc, easily and well integrated. I know its available in some FE's already, but its a classic must have.
3) Quick one-touch access to turning on and off night skin and/or the updating the skin automatically based on GPS time.

[jsn]

Hi Executor485,

Req #1
Will be a hard one to implement for me I think.
We don't have CDMA here, but I might try to set up a plugin system.
This way, another developer might be able to handle the communications
with this device.

Req #2
Ofcourse! But I'll probably concentrate on Garmin Mobile first.
But after that, a poll will decide which will be integrated next.

Req #3
Yeah, got some surprises here. Already implemented the gamma-adjustment
code. The day/night switch will be, in the default skin, on the settings page.
Auto-adjusting the gamma according to the GPS; yes, but probably in a +1.0 version. You can manually set the gamma-level in the configuration.

[Macflurry]

Looks great so far guys, keep it up.

A few quick questions:

Will the front end support keyboard shortcuts for controls so that people can still retain the use of steering controls?

Also with the SatNav side will it be a case of leaving the front end on the SatNav screen and being able to control track changes and volume with the menu bar at the bottom?

If you leave the SatNav screen to go to your media player would it be possible to have junction diagrams pop up in the corner for a couple of seconds, before vanishing, in a similar way to the hidden footer??

Will the music volume be able to dim when a SatNav announcement is made then resume at normal volume once finished??

Will this software support multiple displays so that if you had a second graphics card and an additional screen the SatNav info, or any other designated programs info that could be set in an options screen, could be permanently displayed on there while your primary touch screen would function as normal?? SOme people may want GPS on there or they could set it to output the video display so people with rear screens can watch the film while the driver still has full control of the front end from the primary screen without disturbing the secondary screens display?

Again, really looking forward to seeing this.

Cheers, Stu.

[NoTec]

Yes, we will have most if not all of the sections bound to keystrokes, with a configuration utility to modify and change them to your liking.

For navigation, controlling music on the nav page is ultimate goal and we have a method in place currently that works how your asking, we are just finding out now the best way to make it visually appealing without creating too much clutter on the screen.

As for the volume changing automatically and the duel+ screens, JSN will need to answer those in a followup post to this one. I do however really like that idea of separate screens displaying different information.

Thanks a ton for the feedback and suggestions Macflurry, we really appreciate it.

[jsn]

This 2nd-screen idea is a very good one!
I might be able to let the application always start on the 2nd screen.

About those other features, I really like them too, but it all depends on the
API's of the navigation apps. One might support action notifications, while
another totally doesn't. If it is available, I can probably implement it, but no
garantees yet, this is still an area which needs some more investigation.

Keystrokes are supported, the main-functions of CarMa can be mapped to keys.
Keys can also be programmed to run scripts. Which, in fact, also control about
all aspects of CarMa.

Your other requests won't be such problem, but the volume-adjusting
could be a problem if the navigation app can't notify external apps.

[Macflurry]

Excellent, cheers guys.

[NSFW]

The only things that matter to me are:
* play music, make it easy to select playlists. adding/removing songs from playlists is a secondary consideration, choosing individual songs is dead last.
* support 3rd-party GPS - all I really ask is a 'back' button above the GPS app to return the front end
* phone control - I want to choose a contact and then place a call with the front end, then talk over my headset or (maybe) use the CarPC for audio I/O.
* support 3rd-party engine monitoring stuff - again, all I really want is a topmost 'back' button so it's easy to return to the FE.
* uncluttered UI - not crowded with tons of UI elements on every screen

[Macflurry]

I dont know that many people who actually bother with playlists unless it's used for stacking up albums they've selected back to back.

Most of the time I'd rather just choose my music by the album name or Artist.

[NoTec]

NSFW: Most of your concerns were the exact reasons why I, personally, wanted to build CarMa. I wanted a music / playlist player that just worked. Easy to edit as well.

External 3rd party applications, including GPS, ODBII, etc is already implemented. We are just working on integrating their functions better into the application itself now. But as for any application just sitting inside carma, that is already done.

Uncluttered UI we are working very hard on to try to make it the cleanest UI possible but still having all of the functions available for all the users- by utilizing flyout menus. We will have an advanced mode and a standard mode, which will change some of the pages functions by including more buttons if so desired, but that will not be until after the initial launch.

I will let JNL talk about any plans we have for bluetooth phone support, contact list importing and organizing.