zinc-collective / recipe-box Goto Github PK

OK, so I'm not entirely clear how these things are different. Historically, the UX teams I've worked on have used Indi Young's Mental Models to frame things. I've facilitated a few Story Mapping sessions to get buy in between customers and developers before; but I'm not entirely sure how to translate that experience to an asynchronous process.

This Issue Can Be Closed When

1. We have customer journeys stored in markdown in the project that enumerate three jobs to be done, based on our Personas (see #10)

Absolutely core to the application will be presenting recipes to the user in a useful way. There are a number of websites, apps and good old fashioned cook books that do this incredibly well. I don't think we really need to reinvent the wheel here, but maybe we can take the time to review some existing means of communicating a recipe, as well as noting what features seem most useful while cooking. (Scaling the recipe up or down? Adjusting individual ingredients?)

In order to maintain connection with our community of users needs and wants, we would like to support User Research and Design practitioners performing user research and contributing it to the project.

Open questions:

1. What, if any, projects in the commons make it easy for researchers and designers to contribute?
2. How can we ensure the privacy of research participants is maintained?
3. How can we demonstrate our appreciation for participation in research, given that we have pretty severe capital constraints at the moment?

In order to learn more about how to capture recipes from iOS devices, we want to write an try writing an extension that captures web site data

Choosing a recipe from a set of suggestions is probably the most significant UI-focused part of the application. I'd love to take some time to draw out some rough wireframes and circulate them for feedback.

In order to be confident of the approximate size and shape of the Recipe Box MVP release
As a Contributor
I would like the Maintainers to have a product roadmap with feature definitions and Issues on a Project Board

You may want to reference...

• The How? section of the README
• This insightful thread by @iGoog: #9 (comment)

This Issue May Be Closed When

• We have a set of Epics that encapsulate the top-level features for our MVP that include Gherkin definitions for the use-cases they intend to support so contributors can riff off of and adjust them.
• These issues are organized into a RecipeBox MVP project board held by the @zinc-collective/recipe-box team

There are a number of ways to generate personas, ranging from simply making them up (what I call 'fauxsonas') to performing market or antropological research. For now, I think we're too restricted in labor-power to do a solid job of building research backed personas, but I'd be happy to be wrong.

This issue can be closed when...

We have a PERSONAS.md file in the repository describing the top three people we are designing for with RecipeBox; ordered so that when we're deciding how to build something, we don't detract from the experience of the first persona when building something for the second persona; and we don't detract from the experience of the first and second persona when building something for the third persona.

In order to better understand our market
As a product designer
I would like a set of links to public commentary regarding the pains and dreams that home-cooks experience.

How To Use This Issue

When you see something on the internet talking about cooking from recipes that indicates some frustration or desire, drop a comment here!

In order to figure out what data we have, let's spend a few hours figuring out what data comes out of an h-recipe/hRecipe compatible website, ideally with some working JavaScript or Swift code examples!

At present, we intend to:

1. Export and distribute recipes in the h-recipe microformat, per the recommendations of the IndieWeb wiki entry on recipes.

2. Package a recipes related images into a single file using TextBundle, so that they can be transferred using existing platforms built in data storage and transfer mechanisms.

3. Find (or write) a JavaScript package for parsing recipe data from public websites that works with iOS App Extensions for Browsers

4. Find (or write) a library for accepting TextBundle(s) of recipes in an iOS App Extension

5. Find (or write) a library for parsing a web page into a recipe in an iOS App Extension

We have chosen iOS for our target platform because from our perspective, it has highest standard of user privacy, experience and information security.