Lines Matching refs:to
4 <p>It's important to implement your application so that it will not break as new
7 You can think of these as "anti-patterns" (that is, techniques to avoid) for
13 <p><b>Technique to Avoid, #1: Using Internal APIs</b></p>
17 have chosen to use unsupported or internal APIs. For instance, many
20 fixed in Android 1.5 -- allowed apps to use those APIs without
22 on 1.5. If you've used internal APIs in your apps, you need to update
23 your apps to stop doing so. </p>
25 <p><b>Technique to Avoid, #2: Directly Manipulating Settings</b></p>
28 behavior that we made to Android itself. But we made it because some
36 previously had permission to do so. For instance, apps can no longer
38 question now have no effect, and do nothing. Instead, apps will need to
39 issue an Intent to launch the appropriate Settings configuration
43 Settings that were moved to the Settings.Secure class are affected.
44 Other, less sensitive, settings will continue to have the same behavior
47 <p><b>Technique to Avoid, #3: Going Overboard with Layouts</b></p>
49 <p>Due to changes in the View rendering infrastructure, unreasonably deep
51 layouts are now likely to cause crashes. This was always a risk for
53 better than 1.1 at exposing this problem. Most developers won't need to
55 need to put it on a diet. You can simplify your layouts using the more
58 <p><b>Technique to Avoid, #4: Bad Hardware Assumptions</b></p>
68 <p><b>Technique to Avoid, #5: Incautious Rotations </b></p>
77 device lacks a physical keyboard, these apps do not expect to be
81 <p>Also, apps that use the accelerometer directly to reorient themselves
83 results. And finally, some apps that use the accelerometer to detect
84 things like shaking motions and that don't lock their orientation to
86 orientations. This can be irritating to the user. (You can lock your
87 app's orientation to portrait or landscape using the