Risks differ among private API's. Think from Apple's point of view:
1. You overwrite a method (like Google did), even if Apple changes the API, the app won't crash.
2. You call an selector which is likely to become public (like addTextFieldWithValue).
3. You call an selector whose functionality can be easily reproduced with public API (like addTextFieldWithValue), if Apple changes the API, developer would have to scramble to fix the app but it is doable.
The risk is low for the above three.
4. If you use an undocumented class which is obviously experimental (like MPTVOutWindow), I will bet 99% that it will get rejected until the API becomes public.
|