Planning an app out before starting
I want to make a gong fu cha (tea brewing style, the main thing is that it involves even up to 10 steeps, first ones are short and they're getting progressively longer) timer & steep counter app with a statistics tab. The timer should allow to set a base steep time and an increment to be added each round. The app should allow to see how many brewing sessions there were each month. Each session should have the tea's name in it and a space for flavor and scent description. I'll be using AvaloniaUI and focus on mobile.
I guess I'm going to need some sort of database for the descriptions and saving the sessions, I worked with entity framework and postgresql before.
I want to give test driven development a try, seems like a good thing to know, although I don't know if I'll be able to do it before determining the app's structure down to each function and accurately tell what needs testing and what doesn't.
Did I miss anything important?
6 Replies
Is this a desktop app or a website?
mobile but avalonia is multiplatform iirc
Ah righty, you'll use whatever database your target platform uses, which is probably sqlite
I'm thinking about the unit tests and it's melting my brain a little, seems like a huge leap from general ideas straight down to the smallest building blocks. Does it come easier with experience or is there a special approach? I have some trouble imaging what methods will I need and how they should look like
Yeah, TDD is very much at odds with figuring out stuff as you go! I never got on with it
It's too early to be worrying about tests, either way
Use tests for debugging at this stage