harpy VS obs_blade

It still works mdude try it i use it daily it will go away eventually due to api access like all other clients. But for now its working https://github.com/robertodoering/harpy/releases/tag/0.10.2

(https://github.com/robertodoering/harpy)

Harpy is pretty good imo.

If you have a bit of time, you can add your API key to harpy so you never have to deal with that limit

I'd be happy to have new contributors for my project harpy, a 3rd party twitter client: https://github.com/robertodoering/harpy

Here is my list: 1. Harpy 2. Revanced 3. Twidere 4. spotube 5. immich 6. Noto 7. Florisboard

Try harpy - https://github.com/robertodoering/harpy

I would suggest you take a look at harpy. It's a Twitter client and still seems to be developed (last release was about a month ago).

harpy is a feature rich Twitter client that focuses on a nice user experience and great design. https://github.com/robertodoering/harpy

For controlling OBS, you can control it several ways. If you have a stream deck, you can use OBS web socket. Or if it works, you could just use google chrome Remote Desktop. Might be choppy video though. Also look at obs blade. https://github.com/Kounex/obs_blade

OBS Blade: Make use of the OBS WebSocket Plugin and control your stream

OBS -- I use OBS when I am streaming Graduation/Board Meetings/etc. I use OBS Blade to control it from a tablet.

I'm the author of OBS Blade, an open source mobile app to remotely control OBS (Open Broadcaster Software) which is mainly used for streaming content to platforms like Twitch or YouTube and recording stuff for videos etc!

Just Download the Icon pack as a font (.ttf), include it in your pubspec (take a look here at the bottom: https://github.com/Kounex/obs_blade/blob/master/pubspec.yaml) and create wrapper to use it in a type safe way in your project (https://github.com/Kounex/obs_blade/blob/master/lib/utils/icons/jam_icons.dart)

A general approach is the view / feature driven project structure where the main goal is to separate code / concerns into view / feature specific files / folders. You will usually have some „main“ folders like: utils, types / classes, models, states / stores, widgets / shared etc. But all in all a more freestyle aspect. You can take a look into my open source project for this kind of approach: https://github.com/Kounex/obs_blade but be aware that this is does not guarantee to be a good approach for everyone (or specifically your project). I nested view folders to reflect the way views are direct children (routing wise) and try to extract a lot of stuff into own widgets to keep every widget small and also keep the actual „view widget“ to only serve as laying out the screen.