Define MVP

[adamdoty]

What makes this actually something my wife needs/finds useful?

• tracks birthdays or events that warrant a treat
• provides options if person doesnt know what to pick
• reminds my wife/person if they forget about treat

How does my wife benefit from this app?

• can decide to make an offer and automate part of the process
  • reminders
  • person choosing
  • determining when the offer expires

Essential Features (MVP)

• Baker User

  • catalogue of items for people to pick from (catalogue)
    • submit items already made, interested in making
  • tracking list/calendar of complete, incomplete, future potential offers (coupons) emphasized by wife
  • notifications for upcoming incomplete offers (reminders) added by wife

• Recipient User

  • email reminder (pending coupon)
  • options to pick from (catalogue)
  • ability to request an option not in the catalogue

Extra Features - nice to have but not necessary for MVP

• Recipe cost calculator
• Husband tax, precalculate the portion of scraps that go to yours truly. Determined by my contribution to making the baked good
• Chat (added by wife)

[bbelderbos]

@adamdoty thanks, interesting. Seems quite some features to add, good we got some more scope + clarity.

It seems the baker user side is most developed so far. We just need a boolean on the treat model to indicate it's made (vs interested in making) and show that in the view (making it editable is just a matter of adding the new column to the treat's model form).

For coupons, this will be a new model and view. Will the baker generate coupons manually? Will they be assigned to users, so would each recipient user get a unique coupon assigned? The coupon model is basically an many to many table with two foreign keys then, one to Treat and one to User. I think it should also have an expiration date.

Recipient user: "option to pick from" - that would effectively be redeeming a coupon? Would the coupon code / link be sent through the app? Let's discuss on our next call for more details here ...

What are the first one or two things you want to implement?

[adamdoty]

1. Add choices into the treat model, view, html (I think I want to use choices instead of a boolean in case there are more than 2 values in the future, maybe a proposed by user choice?) I think I am going to pass on this. I don't think its essential for my wife to add goods that haven't been made into the catalogue. It also complicates the treat model as based on the fields, there is an implication that it has been made before. Additionally recipient users can request items not in the catalogue.

[adamdoty]

Does it seem reasonable to finish in 2-3 weeks?

[adamdoty]

2. Add recipe source field into the treat model. This should be an optional field that a link can be placed but not enforced.

[adamdoty]

3. Start coupon model.

[adamdoty]

For the coupon view. I think I want the coupons to manifest within the coupon tracker/calendar (list), and have their own detail ,edit, delete pages.

[bbelderbos]

Does it seem reasonable to finish in 2-3 weeks?

If we scope it down enough and stay consistent yes.

[bbelderbos]

For the coupon view. I think I want the coupons to manifest within the coupon tracker/calendar (list), and have their own detail ,edit, delete pages.

Coupon tracker / calendar? Let's discuss in a bit ...

[bbelderbos]

As discussed: baker makes coupons and can assign them to users. User comes in an on treat list can redeem one or more coupons - nice :)

[adamdoty]

@bbelderbos for the tracker, it would be nice to have both a single month calendar and the coupons on a single page. The calendar would populate with target_dates that occur in that month. If its simple to add a calendar I'd put it in the MVP, if its more complicated, it goes in the nice to have category.

[bbelderbos]

@adamdoty the calendar would show the coupons when they start, end or both? That's for the baker right?

We have a cool calendar for our Organic content creation tool, I think I showed you it. I used https://www.huiwenteo.com/normal/2018/07/24/django-calendar.html for it, maybe worth looking into ...