Thomas Chau’s Post

** Weather App with Auth The app is built using the Model-View-ViewModel (MVVM) architecture. This design pattern separates the concerns of data, UI, and business logic, leading to a more modular and testable codebase. The app's architecture is further enhanced by GetX, a state management library that simplifies reactive programming and state transitions. Daily prediction: the weather now, hourly weather free in each hour, today’s weather, tomorrow’s weather.   All of that support by Tagar#flutterui material widgets. Tagar#flutterMobileDev  #WeatherApp #Authentication #Firebase #FirebaseAuth #Login #Register #MVVM #Apis #VisualCrossing #Hours #Daily #GetX #Mobile #MobileAppDevelopment #Dart #Flutter

𝗦𝘁𝗮𝘁𝗲𝗙𝗹𝗼𝘄 𝘃𝘀 𝗦𝗵𝗮𝗿𝗲𝗱𝗙𝗹𝗼𝘄 🤔 🟣 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗮 𝗳𝗹𝗼𝘄? ⮑ A stream of data that can be computed asynchronously. ⮑ A reactive way to handle data through a pipe for processing. 🟣 𝗦𝘁𝗮𝘁𝗲𝗙𝗹𝗼𝘄 It is a state holder with a single updatable data value. It’s hot and emits the latest value to new subscribers. 🟣 𝗦𝗵𝗮𝗿𝗲𝗱𝗙𝗹𝗼𝘄 ⮑ It is a more flexible hot stream that can emit multiple values and allows for replay and buffering. ✅ 𝗔𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 👉 𝙎𝙩𝙖𝙩𝙚𝙁𝙡𝙤𝙬 ⮑ Only stores the latest value, making it memory-efficient. ⮑ Simple state management; observers automatically get the latest value. 👉 𝙎𝙝𝙖𝙧𝙚𝙙𝙁𝙡𝙤𝙬 ⮑ Supports replay and buffering, making it ideal for events or one-time actions. ⮑ Allows multiple collectors to receive the same value. ⛔ 𝗗𝗶𝘀𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 👉 𝙎𝙩𝙖𝙩𝙚𝙁𝙡𝙤𝙬 ⮑ Limited to a single value; not ideal for event-based flows. ⮑ Doesn’t support replay beyond the latest value. 👉 𝙎𝙝𝙖𝙧𝙚𝙙𝙁𝙡𝙤𝙬 ⮑ Requires configuration for buffering, which may increase memory usage. ⮑ More complex than StateFlow for simple state management. 🚀 𝗖𝗼𝗻𝗰𝗹𝘂𝘀𝗶𝗼𝗻 👉 𝙎𝙩𝙖𝙩𝙚𝙁𝙡𝙤𝙬 ⮑ Ideal for representing UI state that needs to persist and update over time. ⮑ Use it for state-driven UIs where the latest value is always relevant. 👉 𝙎𝙝𝙖𝙧𝙚𝙙𝙁𝙡𝙤𝙬 ⮑ Use it when you need multiple subscribers to receive the same value. ⮑ Perfect for scenarios needing replay and buffering capabilities. 𝗜𝗳 𝘆𝗼𝘂 𝗳𝗼𝘂𝗻𝗱 𝘁𝗵𝗶𝘀 𝘃𝗮𝗹𝘂𝗮𝗯𝗹𝗲: 𝘓𝘪𝘬𝘦 👍 Comment 💬 Repost 🚀 #Android #AndroidDevelopment #Kotlin

User behavior is difficult to predict, so how do you test for it By talking regularly to your users and the support teams as they hear the complaints first #softwaretesting #testautomation #userexpereince

Engineers and product managers don’t get enough love for establishing best in class exception and error handling. Make documentation a first class citizen.

Today, I learned about Socket.io, focusing on its ability to manage persistent HTTP requests and enable bi-directional communication. I also explored how Socket.io establishes a continuous pipeline between the client and server. Additionally, I discovered that Socket.io operates on an event-driven architecture. #socket #websocket #webdev #fullstackdev #chatapp 👇Video of the chat app made using socket io

Thrilled to announce⚡️ Request Prioritization support for `/v1/completion` route - https://lnkd.in/danZzB3S (+4 more updates 👇) 🚀 WatsonX - ZenAPIKey Auth support ✅ Prompt Management - proxy provider route fix 👋 `get_valid_models()` - Returns all `litellm_proxy/` models 💪 UI - fix displaying new keys by Admin

In the original #Angular version of my Incident Commander app, I was using a Single-Page Application (SPA) architecture; which allowed the primary input to never lose focus. Now that I've rewritten the app using as a #ColdFusion Multi-Page Application (MPA) architecture, I have to consider focus management; and, considering that I've just finished reading "What Every Engineer Should Know About Digital Accessibility", I'm trying to do so with an eye towards #Accessible: Read more: https://bennadel.com/4739 My initial thought was to just throw `autofocus` on the textarea and call it a day. But, my post-submission success message is an #ARIA live region; and I'm worried that 1) moving focus will interrupt any assistive technology (AT) that might be announcing the message and 2) automatically moving focus around the document might disorienting for AT navigation. What I've decided to do is use #AlpineJS to listen for a global keyboard event (C), to allow explicit control over the focus, moving it back to the textarea only when the user wants it to take place.

#discussion #mvvm #statemanagement Edit: I am more interested in an architectural answer than how to observe singleton of data object from anywhere. It is about where to put the thing (data, store, whatever the answer) in an MVVM. ---- Post: How to integrate a state management approach into mvvm arch (UIKit) that does not bring the complexity of redux-like archs .. You know, we have VIPER that provides a router component to handle advanced communication .. but yet we can implement Coordinator pattern to take this role in mvvm .. I wonder why not we do such for state management .. as simple as possibel for not complex use cases but still painful to be handled by mvvm alone. For an e-commerce app, there is a global cart state to be managed between different parts kf the app (not even siblings or ancestors) .. and other use cases for a booking application. I am looking for a less complex approch than reducers, actions, etc that strictly follow patterns of the web, providing too much abstraction, and we even have no testing getting done for such complete state management archs. I would appreciate an open discussion or resources to expand my knowledge on this.

Round Trip Time (RRT) now available in CrUX! RRT has been added to the CrUX API, so I've added it to my core web vitals history tool here: https://lnkd.in/eFxCNZrA There's no 'Official' guidelines for good or poor, so currently I've kind of pick some that make sense, these thresholds will definitely change over time! In case you're wondering, RRT is a measure of latency, and the time it takes for a request to go from your users browser, to your server (or CDN) and back again. It's a part of what makes up TTFB, and looking at both together can help you understand where you need to improve, so my tool also gives you a chart of TTFB & RTT, if you're seeing TTFB getting worse and RTT climbing, perhaps time to look at where your users are coming from and if you need to use a CDN with a point of presence closer to that market. CrUX docs on RTT: https://lnkd.in/efqpUVGR More about RTT in general: https://lnkd.in/ewTQwvrm #WebPerf #CrUX

In the original #Angular version of my Incident Commander app, I was using a Single-Page Application (SPA) architecture; which allowed the primary input to never lose focus. Now that I've rewritten the app using as a #ColdFusion Multi-Page Application (MPA) architecture, I have to consider focus management; and, considering that I've just finished reading "What Every Engineer Should Know About Digital Accessibility", I'm trying to do so with an eye towards #Accessible: Read more: https://bennadel.com/4739 My initial thought was to just throw `autofocus` on the textarea and call it a day. But, my post-submission success message is an #ARIA live region; and I'm worried that 1) moving focus will interrupt any assistive technology (AT) that might be announcing the message and 2) automatically moving focus around the document might disorienting for AT navigation. What I've decided to do is use #AlpineJS to listen for a global keyboard event (C), to allow explicit control over the focus, moving it back to the textarea only when the user wants it to take place.