Is there a best practice for using Data Wedge in a complex native app with many input fields?
I have field dependent validation rules and some data will have to be parsed so it doesn't seem like a good idea to just let DataWedge use keystrokes to put the scanned value in which ever field has focus. But it seems overkill to use intents and create a seperate profile for each field switching between them as the focus changes. The samples I've seen don't make any attempt to identify the destination of the data being collected so I'm not sure what method is preffered. Any thoughts appreciated.