New post on /r/flutterdev subreddit:
<b>[Release | Open Source] OBS Blade - Control your OBS instance and manage your stream - live!</b>
Greetings everyone,I finally managed to get OBS Blade up on both app stores and I wanted to share this one with you since this app is open source and some of you may be interested in a live example! :)Most important stuff<a href="
https://obsproject.com/">OBS</a> (Open Broadcaster Software) can be used to stream to various platforms (like Twitch / Youtube) and has a lot of convenience features like creating different scenes to switch to, add designated sources to use / show and much more. OBS Blade makes use of the awesome <a href="
https://github.com/Palakis/obs-websocket">OBS WebSocket</a> plugin (which is open source as well) to communicate with OBS remotely.For everyone who wants to read more about it and see some code / build this boy:<a href="
https://github.com/Kounex/obs_blade">GitHub</a>For everyone who wants to download it instead of building it on their own:<a href="
https://apps.apple.com/de/app/obs-blade/id1523915884?l=en">iOS App Store</a><a href="
https://play.google.com/store/apps/details?id=com.kounex.obs_blade">Google Play Store</a>Some loreAs everyone else, my girlfriend and I went into lockdown earlier this year which inspired us to try out streaming some gaming related stuff. After the initial setup and some testing we had a working OBS environment where we could switch scenes to show either her screen or mine while streaming on one account. Since I had to switch to OBS pretty often to switch scenes, I always had to "tab out" the game to do so which was far from optimal. After some research I found this awesome WebSocket plugin I mentioned earlier which lists some implementations using it (which includes a live Javascript one). For a while I placed a tablet right in front of me (much like one of those stream decks) had the Javascript powered site opened which was connected to my OBS instance and could change the active scene on the fly - pretty nice.Since I had to visit the page every time, put in my local ip address manually and the implementation was missing some features I wanted (spoiler: the current version of my app does not have significantly more features, lol) I took this opportunity to turn this into a passion project by writing a Flutter app for that! I have been using Flutter since somewhen 2017ish and wrote some helper apps for personal use so this option was kinda natural.Tech infosNow the interesting part: following a list of some noteworthy decisions / parts of the app mostly related to Flutter. As a side note: I wrote a lot of comments throughout the app's source code to explain certain decisions, if you encounter parts which are not clear just let me know and I add some more! :)<strong>State management solution: MobX + Provider</strong>In the past I tried several approaches to maintain some form of app / feature states like BloC, Redux, States Rebuilder, purely Provider and classic Inherited Widget + ChangeNotifier (and Riverpod lately). In other frameworks / languages in the past I usually didn't pay too much attention to this topic since in those cases the environment itself kinda got this covered (at least in some way). Since Flutter has a very minimalistic and straightforward approach, the first steps are usually easy but scaling into bigger projects can get messy real fast if certain decisions about project structure (especially logically wise) are not made. The decision about how to store runtime information, how to access it and, in the Flutter context, how to update the UI accordingly is crucial. All of the solutions (and many more) are suitable and a lot comes down to personal preference! The reason I chose MobX is, that the way of writing classes (which will represent some kind of states) feels very native thanks to the annotations + code generator approach and updating the UI with the Observer widget is pure bliss. To implement dynamic stuff (like…