In short, no. People without the literacy needed to evaluate a design by looking at wireframes can't give you a good answer. The only way to get a real answer from your target audience is to test the design with them. Otherwise it's like a doctor asking a patient which treatment they prefer, rather than saying 'this is what you need.'
Testing doesn't have to be a big and expensive deal, either. You can go as simple as wireframing the screens and dialogs needed for a given task and asking them to 'tap' through them by pointing to screen elements and telling you what they are thinking as they do. Make notes about what they get right, and what wasn't clear to them, and revise. Read up on paper prototyping for some tips on how to go about this.
To go one step better, get the design prototyped so that your test audience can use it on a screen, and see how it goes. It's more time consuming, especially if you don't code yourself, but it's very effective.
You can also be quite limited with your test audience; 3-5 people will find the majority of problems, based on research by Jakob Neilsen. Even if you can only get one person who will be an actual user of the product, it will help you much more than asking them what they prefer. Testing is part of going the distance to producing good designs, and asking for preference seems almost likely to produce the opposite of a successful design.