A household goes through tons of "consumables": food, toilet paper, laundry detergent,
you name it. It is a huge challenge for households to track and manage these daily needs.
Though various household members are moving around the city all day --- and could potentially
make efficient on-the-way purchases --- in reality, no one knows or can remember what needs
to be purchased and who is supposed to purchase it. Which means wasted time, extra trips to
the store for one item, and general frustration about eating dry cereal, washing your hair with
facial soap, and wiping your bottom with paper towels. We've all been there. Or worse yet,
multiple people remember to buy and you end up with 400 rolls of toilet paper. iBuy will solve
this problem forever.
General functional requirements.
Overview: It's hard to believe that, in this modern age of wireless networking and on-thego
computing, we haven't come up with something better than the back of an envelope to
keep track of the groceries we need to buy. What is needed is an integrated solution that
lets you enter/add/edit items on any device, any time, any place, with instant sync shown
on other devices. Of course, usability is the key. It has to be ultra-simple to put information
into the system, manage it, and extract it efficiently on demand. If there is not substantial
value added over the old back-of-the-envelope method --- and that value is not immediately
apparent/usable by the target population --- the application will fail.
This project involves designing a clean and simple purchase management system. The
networked, multi-interface aspect of the system is key: the whole point is that you can
record purchasing needs when/where they occur to you, using whatever device is most
convenient at the moment, and then consult and check off those needs later, on demand,
wherever you are, and using whatever device is best suited to your needs. This doesn't
mean, however, that each interface has to support all functions --- clever design will
determine what is appropriate.
The exact functionality of this module, of course, will be something that you will need to
determine in your design process, in collaboration with your end-user community. The
bottom line is that you must be able to justify any functionality you put in (or leave
out). However, it's useful to give just a sketch to give you an idea of the different
"ballparks" of complexity I expect to see, to give you an idea of grades you can expect for
your work. You can then mix up and add/delete features based on what your research finds
that users want; find out what users want and need and design an integrated package.
4 freelancers are bidding on average $251 for this job
Hi I have been in this industry for 5 years and such jobs are my daily practice.I can assure you that if you work with me once, you will always work with me for these kind of projects.