Was thinking a lot about the UX for my DAW and tried different approaches. I think I came up with a pretty cool solution.
- You get a grid of items, where you can place different things
- Things can be tracks, samples, parameters, etc.
- You can play and stop things individually
- You can use tracks etc in other tracks.
This gives you a lot of flexibility while being easy to understand.
One major issue with that is that sections can have different lengths, so each track needs its own timeline. This made me think about each track having its own playhead ๐ค
Thinking about different user experiences/UIs.
- I don't like different kind of views as in logic pro or FL, so I restrict it to 1
- Full songs need a play head, so that means my view needs a play head, too
- I want to support creating different variations of the same thing, as that makes music interesting
Playing with the idea of defining sections in the timeline and add controls for loop etc for each section. That fulfils the requirements of having a play head and being able to duplicate sections and making variations.
Added play head controls for controlling play position.
- To reduce cpu usage the audio thread sends the play position only every ~0.3 seconds
- The UI receives that and updates the play head to the actual position
- To get a smooth movement I use requestAnimationFrame and advance the position only in the UI
Started vibe coding it but it messed up quite a lot. It's pretty good generating UI, but other than that it's annoying correcting its mistakes. So now I use AI for some bits and pieces, but doing the important stuff myself.
@thekitze Thing is statistically itโs true that these things arenโt good. But stats donโt mean anything when you only look at one sample (person). All this stuff is very individual.
@aniemmadi@y_molodtsov@aarondfrancis Itโs well researched and it affects it, but people misunderstand. You want blue light during the day, and you wanna avoid it during the night. Avoiding it all the time is wrong. Hubermann says that too as far as I remember.
@eklipsedev@medusajs Agree. Would add that many underestimate how much data a modern device can handle. If your data set is under a couple of thousand rows I wouldnโt even bother thinking about server side filtering. One thing to keep in mind is the payload size you send to the client.
@daniel_nguyenx But supabase is only free for the first 2 projects (at least thatโs how it used to be). With D1 I can have multiple dbs if below the free tier.
I need an app:
- I hit a button and it opens X
- at the same time it starts a timer
- after some time, eg 60s, it sends a notification. I hit it, it takes me back, the timer stops
- I can repeat that
For what? I like doing social media during workouts, but I get distracted and pause for too long
@deedydas Cool post how about how. ๐ can you explain WHY youโd wanna start a US company as an international founder? Iโm considering but donโt know pros vs cons