I'm developing an iPhone app that uses pretty standard UI, follows Apple's human-interface guidelines, and in some cases imitates behavior as seen in stock iPhone apps. For example, a table view from which rows can be deleted by either using swipe to delete, or by tapping the edit button in the top right corner. Another example would be a label with underlined text that can be tapped to show a different screen, if a button is just a little too much.
The app hasn't officially launched yet, but some people in management have the app on their devices. These folks don't know much about their phones, though. More than 18 months after introduction of notification center in iOS 5, my boss was surprised when he saw me pull that down. He'd never seen that before. Just recently he asked me how I knew that my phone wasn't connected to WiFi, while the status bar has indicated this since June 27, 2007.
The problem lies in that these same people give me feedback that certain things in my app aren't intuitive. I use the underlined label once, but he and some other people who have access to pre-release versions didn't realize it could be tapped.
The big question is: can I as a developer use commonly used UI elements and paradigms, assuming that the user is familiar with these, or should I point out every tiny detail ("you can tap this button to go here" and "you can select this row to go to screen x or tap the accessory button on that row to go to screen y")?