2.16.1 Use of Applets
The applets are designed for the purpose of assisting with the implementation of application features, but you are not required to use the applets. Even in parts of the application that could make use of the features the applets provide, you are free to choose whether to have the application use the applets.
No required guideline items.
2.16.2 Displaying an Application Screenshot While an Applet Is in Use
When an application calls an applet, one screen (either the upper or lower screen) shows the applet and the other screen shows an image (screenshot) of the application captured when the applet was called. The application cannot render to the screen or update the captured image while the applet is running. We therefore recommend that applications hide anything that would not be desirable to leave onscreen without an update, such as the time or remaining battery life, before invoking an applet.
No required guideline items.
2.16.3 Software Keyboard Applet
Currently there are no particular precautions regarding the software keyboard applet.
No required guideline items.
2.16.4 Error/EULA Applet
You can use the error/EULA applet to display infrastructure communication errors, other optional error messages, and the EULA agreement sequence.
If your application uses Nintendo 3DS communication features, your application is required to be able to display infrastructure communication errors and the EULA agreement sequence. See the guidelines concerning communication features, such as volumes 5 StreetPass and Local Communication and 6 Internet Communication, for information regarding these features.
These requirements do not apply when displaying other error messages.
No required guideline items.