Here are a few of the most common questions new developers have around the SmartDeviceLink project.
WiFi transports are supported in two ways with various limitations. First, the production version is only available as a secondary transport. This means that a primary transport (such as Bluetooth or USB) has to be connected first in order for the TCP transport to connect.
Secondly, this transport can be used in the development and debugging phase of SDL integration and will act as the primary transport in that situation. For more information please see the evolution proposal SDL 0141: Supporting simultaneous multiple transports.
This is possible, but not recommended as any app that builds itself for the head unit's custom template would not work with any other systems. If new templates are desired, they should go through the SDL Evolution Process and be adopted by the project.
This is possible, but not recommended as any app that builds itself for the head unit's custom vehicle data types would not work with any other systems. If new vehicle data types are desired, they should go through the SDL Evolution Process and be adopted by the project.
To obtain an App ID, you must first register for an account on the SDL Developer Portal, and then register the company to which the app should belong. Once your company is registered, you can select the App IDs tab from your company profile and click the "Create New App ID" button to provide your app information and obtain your App ID.
Templates are the best way for you to design your application with the driver's safety in mind. For more information on the benefits of templates, please see this document.
Each project has documentation, guides, and may have their own FAQ that can help. If you still need help, please join the SmartDeviceLink Slack team and ask your question.View on GitHub.com