People: I will never put one of those smart speakers in my home! You're basically just putting in a microphone that will spy on you!

Also People: Hang on I have to grab my phone/high-fidelity microphone/high resolution camera/GPS tracker/Data Aggregator and make sure I have it with me literally everywhere I go, because who knows when I will want to comment on a cute picture of a cat!?

"Build high fidelity apps" such as the ionic website...

What I was supposed to do today:

Finish up some homework and code for a bit

What I actually did today:

1. Boot up my laptop to get started on homework

2. Open Spotify and try to connect my headphones

3. Reinstall Bluetooth and pulseaudio to connect to headphones

4. Connected! But the sound quality is shit

5. Spend an hour or so learning about codec sinks and how Bluetooth is the definition of an overengineered clusterfuck

6. Install some package from the aur to get AAC codec support

7. Now we have high fidelity audio, but the headphones still connect to the crappy SBC sink, so I spend another 45 minutes writing a shell script to automatically switch to the AAC sink when a Bluetooth headset connects

8. It’s finally working! But now I have no motivation to do my actual work. Fml

When everyone thinks FE is easier, quicker, and less important than BE. Just because our fantastic UX people made you a high fidelity mockup in a day does not mean we can build the whole FE in a week.

This is why I'm returning to full stack.

TL;DR: Have you ever been on a serious company where you have to DRAW a high fidelity mockup of the software in the design phase?

So I'm in my last year of college and I have a class called Interactive systems design, which is basically about usability and how to design the frontend of your app so it's intuitive, pretty and easy to use.

So we work in groups to design a project for the entire semester, following a long and tedious process of research and planning which includes writing absurdly long documents, doing interviews with potential users and more.
Now that we've done all of that, the teacher insists that we make paper mockups of our app before we do a digital one using Balsamiq or other programs. He wants the paper mockups to be "interactive", so we have to draw them and then record a video where someone "clicks" on the mockup with their fingers and another person moves the papers around to make it look like an actual app that's doing something.

The teacher still insists this is something almost every company does when designing a project, so it's very important that we learn to do this kind of stuff. He's kidding, right? Have you guys ever drawn a mockup of an app instead of using some mockup software?

I was wondering how I can go about with the development of an Android app.
I've made a few small apps, but I want to make something a little more complex.

I've made the use case diagrams, high-fidelity prototypes and the database schema is almost ready.

I'm just stuck with how to model the app. Which architecture to use? How to actually implement a complex project?

Display quality is a realm where Apple's options are straight up bargains, the cheapest thing to exist.
All I want is a display that ticks all the boxes: it has true blacks (probably OLED), high PPI (more than 200), high refresh rate (more than 120 hz), and good enough colors for graphic design. At $2,499, MacBook Pro 16 is an offering no one can touch.

I'm yet to find an external display that can match it. Gaming displays that have the refresh rate lack in color fidelity and PPI. Designer displays with good colors are almost all IPS and are all 60 hz.

Even if this godforsaken external display exists, it sure as hell costs more than 2.5k, and it doesn't even come with one of the best laptop CPU/GPU there is.