I use parent and sub-contexts for this to some degree....
I have an "Errands" context that contains contexts for Grocery Store, Pharmacy, etc. Most things I tend to buy in only one generic place (I don't necessarily label my Grocery Store as a specific grocery store, but rather just any Grocery Store I happen to be at).
Items that can be done anywhere, or in more than one place, go into the parent context ("Errands"), while items that are more location-specific land in their appropriate sub-context.
As an aside, I find getting too store-specific creates more confusion than it solves.... If I can't find something I want at the grocery store I'm at, it's no harm to just leave it unchecked until my next grocery trip. Ergo, things like "Grocery Store" and "Convenience Store" would likely all fall into "Grocery Store" in my world. On the other hand, tasks like "Buy Milk" (ie, routine staples) tend to go into the "Errands" context so they're combined with my general errands and not just store-specific trips (in other words, I may need to stop off somewhere and buy milk when running other errands, but not necessarily specifically going to the Grocery Store).
In OF on the desktop, I simply select the "Errands" context and I see everything in the sub-contexts right htere. I can group by context if I want to separate them out logically, but they're still shown on the same listing.
When viewing this on the iPhone, I can easily move up and down, rather than laterally, to see those things that are sub-context specific as opposed to more generic. It saves a step, and of course you can still see the subcontexts listed from the parent context with the number of available items shown in each.
If you had a lot of different grocery/food stores that you bought specific items at, then you could just nest one level deeper: Grocery Stores could have additional sub-contexts for store-specific items.
I do similar things with my Calls contexts (sub-contexts for business and personal), and some of my "Household" tasks as well (based on location or situation within the house).
While not ideal compared to multiple contexts, it's not an unreasonable workaround.
I have an "Errands" context that contains contexts for Grocery Store, Pharmacy, etc. Most things I tend to buy in only one generic place (I don't necessarily label my Grocery Store as a specific grocery store, but rather just any Grocery Store I happen to be at).
Items that can be done anywhere, or in more than one place, go into the parent context ("Errands"), while items that are more location-specific land in their appropriate sub-context.
As an aside, I find getting too store-specific creates more confusion than it solves.... If I can't find something I want at the grocery store I'm at, it's no harm to just leave it unchecked until my next grocery trip. Ergo, things like "Grocery Store" and "Convenience Store" would likely all fall into "Grocery Store" in my world. On the other hand, tasks like "Buy Milk" (ie, routine staples) tend to go into the "Errands" context so they're combined with my general errands and not just store-specific trips (in other words, I may need to stop off somewhere and buy milk when running other errands, but not necessarily specifically going to the Grocery Store).
In OF on the desktop, I simply select the "Errands" context and I see everything in the sub-contexts right htere. I can group by context if I want to separate them out logically, but they're still shown on the same listing.
When viewing this on the iPhone, I can easily move up and down, rather than laterally, to see those things that are sub-context specific as opposed to more generic. It saves a step, and of course you can still see the subcontexts listed from the parent context with the number of available items shown in each.
If you had a lot of different grocery/food stores that you bought specific items at, then you could just nest one level deeper: Grocery Stores could have additional sub-contexts for store-specific items.
I do similar things with my Calls contexts (sub-contexts for business and personal), and some of my "Household" tasks as well (based on location or situation within the house).
While not ideal compared to multiple contexts, it's not an unreasonable workaround.