I have an existing iPhone app that lets users share information via links sent through email. I would like to add support for sharing the same information through bump, hoccer, and by displaying a QR code on one phone that would be read by another phone. QR code reader support should use the ZBar library.
The URLs will take the form of HTTP://[url removed, login to view] You will need to verify that code points to a valid entity in our system and then pass the code to another view controller that will display the relevant information.
The application can also be used to manage gift cards and customer loyalty programs. This project only deals with coupons. You can find the application in the app store by searching for "DRI Wallet"
The application is already designed and functional. There are no mockups for this new functionality. We have a share button on a screen that currently just brings up an email compose window. It was my intention to change the share button to bring up a UIActionSheet that would have 4 buttons on it: email, QR Code, bump, and hoccer.
Hitting email would just call the code that's already in there for email. QR Code would display a new view that shows a standard back button on a blue bar, the QR Code, and a label under the QR Code that will contain instructions that we will write up and either send you or just add in later. Hitting bump will display the standard bump screen which I think is included in their SDK. Hoccer will do the same except display hoccer's screen.
That's all on the sender's side. The receiver's side would be a little different. Any time the user shakes their phone (except when editing a text field) a menu will pop up asking how they want to receive the coupon. QR will bring up the ZBar scanner UI. Bump will display the bump screen for receiving. Hoccer will display their screen if one is included. I am currently looking into whether or not hoccer provides the UI elements necessary or if I would need to provide them for you. I don't expect you to do any graphic work.
This app only runs in portrait orientation and does not run on the iPad so you will not have to support either of those.
We have also looked into purposefully degrading our QR codes so we can mark them as DRI codes much like the BBC does. Please let me know if you think you can do this.
1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's Worker Legal Agreement).
2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment.
b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project.