There's no bad interview question, but there are certainly bad interview _processes_. We use a whiteboard session as the last step in the technical interview, and we're really not looking for someone to write functioning code, we're looking for the candidate's thought process as they lay out a design for a simple OO program.
For the type of programming I'm involved in hiring (iOS/Android) it's silly to expect someone not to lean on frameworks/IDEs. It's also unrealistic to expect that every single candidate has a laptop fully set up with their preferred environment. That's what take-home questions are for.
For the type of programming I'm involved in hiring (iOS/Android) it's silly to expect someone not to lean on frameworks/IDEs. It's also unrealistic to expect that every single candidate has a laptop fully set up with their preferred environment. That's what take-home questions are for.