Robert Odrowaz

Three talks. Two speakers. Huge shout-out to @mchudy_ and @RobertOdrowaz for representing LeanCode at @FlutterconWorld India and delivering talks packed with real-world Flutter insights. 🚀 As we’ve heard, the energy of #ftconin25 and the India Flutter community was great - thank you for all the conversations and questions. Flutter connects people across the globe. ✨ #FlutterDev #FlutterCommunity #FlutterConference

We’re heading somewhere we haven’t been as LeanCode yet: ✨ our team is flying to @FlutterconWorld India with three talks! On Dec 14, two of our Senior Flutter Devs will share battle-tested knowledge with the Flutter community: 🎤 @mchudy_: 🔹 Escaping Chaos: From Polyrepo to Monorepo 🔹 Timing Legacy: Refactoring Patterns for Large Flutter Codebases 🎤 @RobertOdrowaz: 🔹 Using Dart FFI for Compute-Heavy Tasks in Flutter Apps If you’re attending, join their sessions, say hi, and give them a well-deserved high-five! 🙌 #FlutterDev #FlutterConference #FlutterCommunity #ftconin25

Only one chance to catch @RobertOdrowaz from @LeanCodePl at #ftconin25 🇮🇳 Learn from one of the best in #Flutter, as they help you #FlutterDevs boost your #app’s performance! Discover how #Dart FFI bridges Dart with C for serious speed gains. Get your front-row seat—tickets on sale now! india.fluttercon.dev/speakers/rober…

🎤Last Thursday, @RobertOdrowaz from LeanCode took the stage at @FlutterconWorld NYC! It's always great to see our team sharing knowledge on international stages.🌍 Also a big thank you to everyone who attended the session - it was great to connect with fellow Flutter enthusiasts at #ftcon25usa! #Flutter #Dart #FlutterDev #MobileDevelopment

Thrilled to have @RobertOdrowaz hit the #ftcon25usa stage! 👏 Boost #Flutter performance with #Dart FFI! Learn to integrate faster C code for compute-heavy tasks while using Dart for the rest. flutterconusa.dev/speakers/rober…

@son_of_agah All FAANG/FAAMG services do this except for Apple. But even Apple, like most websites, leaks whether the account exists when you try to reset the password

i signed up on this one website. before logging in, i accidentally typed the wrong password and i got “password incorrect” so i was like cool, let me try a wrong email too then boom, “user doesn’t exist”. oya nau. you’ve basically just made life easier for brute force attackers.

Does anyone know how to get this card authentication to work on Apple Search Ads? I've already tried different cards from different institutions and payment networks, different operating systems and browsers. Do I really need to get a non-EU card?

@luke_pighetti I don't think it explicitly uses English; it uses the format from the template ARB file, same as all other metadata. It definitely could be documented better, but I don't know what else a template ARB file would mean if not that it defines metadata

oops lol github.com/flutter/flutte…

@luke_pighetti I don't think it's the best solution. Instead, you should use `behavior: HitTestBehavior.opaque` in `GestureDetector`

another thing that confuses the heck out of newbies and causes tiny tap targets

This is new. I've managed to fill up all the disk space on a GitHub Actions runner while building a Flutter app 🙈

@_JohnHammond Wouldn't sending a unique (per-user) but constant keyword in emails greatly simplify identifying phishing emails? For example, I would know that an email is likely legitimate if it includes 'cucumber' because only X knows that's my keyword. Why isn't this a thing?

Wait, what is the sender address & the link URL in this email? I don't know why this didn't occur to me until someone commented, but, is this the phishing email itself? Was I misunderstanding the tweet? Does anyone have a recent legitimate x dot com new login email notice?

@ASalvadorini @OrestesGaolin @RydMike The behavior AFAIK is: when a widget gets invalidated, all of its children rebuild by default. If a child is const, it stops the rebuild of a given subtree. But some widgets in the subtree can also be invalidated, again triggering a rebuild of some part of the subtree

@ASalvadorini @OrestesGaolin I'm not sure if you mean that theme and localisation are special cases, but they are not; it's true for all InheritedWidgets, including Provider, MediaQuery, etc., as @RydMike commented

I think it's quite important optimization to remember about const widgets that they actually won't get rebuilt when you rebuild the parent widget. Using non-const will rebuild the entire subtree of non-const widgets.

@ASalvadorini @OrestesGaolin I believe the way @OrestesGaolin put it is precisely correct: "won't get rebuilt when you rebuild the parent widget," but it may rebuild for other reasons

@RobertOdrowaz @OrestesGaolin No I don't think that's possible. If you think so, show me the code. A const widget cannot be built twice afaik

@ASalvadorini @OrestesGaolin I don't think the reasoning based on memory allocation is correct. A const widget will be allocated only once but can still be rebuilt, for example, due to a change in the context it depends on

@OrestesGaolin I think it's much easier to reason about const widgets with memory allocation. Const widgets get memory allocated once and only once. Which has the consequence you're saying, no matter how often you rebuild the tree they belong to, they are never rebuilt (they're constant) 👍

✅ Non-subscription product price management for PricingCat.com done. Only one feature left on the roadmap before the end of beta

✨Flutter CTO Report 2024 is here! ✨Download it today! leancode.co/flutter-report Inside: 👀 How much faster is #Flutter? 👀 What is the biggest obstacle when starting with Flutter? 👀 How popular is Flutter for Web and other platforms? 👀 and much more!

@marcmacias96 @yasfdany For the record, there are tokens that are intended to be used directly by the client app. For example, Google Maps SDK keys. In those cases, there may be other mechanisms to reduce the risk of unauthorized use #restricting-api-keys" target="_blank" rel="nofollow noopener">developers.google.com/maps/api-secur…

@marcmacias96 @yasfdany If it's a token that a user shouldn't be able to access, the only way is to make requests from the backend. The client app calls the backend, which authenticates the user, enforces quotas, etc., and then the backend calls the third-party API

Don't use flutter_dotenv, it's not really secure, why? - build your apk - rename the file extension to zip - extract it And you'll know why