Because It Works
Why Build MyShopper? Mainly because of problems with SmartPhone Apps, with point #1 being non-unique items by Cart or Store or User. Number 2 is concise Store Location feature for an item. There are many more, but solving #1 and #2 makes use in-the-store much easier.
Problem #1 solution is making the item unique. Initial design was unique per the Shopping Cart. However, that will be refined in future releases as deemed necessary. Current uniqueness thinking is Cart – Store – Item. However, pre-release versions have the database design and indices complete, but not enabled.
Problem #2 solution is best shown by the Walmart model currently provided in the demo.
Methodology of MyShopper uses a design and build model, whereby portions are designed, built and then tested against business rules, before moving to the next phase. When complete MyShopper should meet the overall business rules and objectives.
My Feedback Since Writing MyShopper App!
Using MyShopper at four stores has saved time, and most notably at Walmart and Costco.
Fave On at the store is perfect for us. Find a few items and change their status. Here, too, bulk mode can save time. Yes, it needs to be written, especially without Store WiFi service.
Faves Off grocery lists can be updated to On anytime or before heading to the store.
Try it on the demo.
Fave changing in bulk mode? Yes, but at home, no advantage with good WiFi and Web Server.
Single vs Multiple Shopping Cart Interface? Difficult to say with just two of us. However, most of the structure is already written and another developer could do it.
Release to Developers? Probably 1st quarter 2025 or by individual request.
Developer Can Craft Their Way!
One Intended Benefit! A great Application for developers to make it their own.