Skip to main content

Command Palette

Search for a command to run...

Requirements

Published
1 min read

It’s hard for me to switch mental context between problem thinking and solution thinking. Design thinking and building thinking.

It seems like I’d be able to sit down and bang out v1 of my app, but it’s really not that simple.

How do you take a high level idea and break it down into tangible requirements? One way is to capture use cases. I took a pretty interesting course through Udemy which was basically a refresher of other software requirements classes I’ve taken before.

UC-a3f20082-5625-4da5-8914-7fe66ada14a5.jpg

I love the idea of just thinking through a user journey or scenario and capturing a high level summary. Another concept they went into is performing an event-response analysis to find requirements.

I just jotted down a few things of the top of my mind to capture areas I need to go back and break down in more detail. Some of these might never make it into v1. And there might be others that I haven’t uncovered yet.

unnamed.jpg

I’m starting a 4 week UX design class through Coursera / Google soon. It should be interesting (and very new for me) to take some of these ideas and get them down onto a mobile canvas.

https://www.coursera.org/professional-certificates/google-ux-design

Building in public

Part 8 of 10

Follow my professional development journey, bringing an idea to market. Cozy weather takes "feels like" forecasts to the next level by helping you build your own personal temperature profile.

Up next

Baby steps

Basic infrastructure is in place! I'm using this CleanArchitecture template as the basis of the project. It's running here: https://cozyweather.com/ Next steps include retooling the front end to run a NativeScript project rather than just plain Ang...