# API Brainstorm ## Non-Technical - This is a full-fledged product - Requires design on every aspect of it - Not just an Engineering task - Who is this targeted for? - What is it's business model? - What's the overarching goal of the API? - Which API can we take inspiration from? - Do we need more information / expertise? - Consultants - We need product requirements - Prioritize - Product Requirements -> Features -> Stories - Hypothesis -> Experiments -> something I forget - What do we think will we important? - What is the smallest experiment to prove it? - How can we do market research? ## Technical We should tread these carefully until we have *prioritized* product requirements. - What is our collective API Knowledge base? - What are our major technical challenges that will come up? - What design patterns should we employ? - What major technologies will we use? - What new technologies do we need to learn?