![Souhail Marghabi Profile](https://pbs.twimg.com/profile_images/1603514896410353679/_nhv2Sq1_x96.jpg)
Souhail Marghabi
@thegintalord
Followers
99
Following
5K
Statuses
774
Sr. Mobile Engineer, 10+ yrs. Passion for mobile tech, UX & innovation. Expertise in iOS Swift, Kotlin & Flutter. Always learning, always pushing limits. 📱🚀
Munich, Bavaria
Joined November 2018
@ue_man With things like freezed or json serializer you dont have the chance to set that yourself. I usually run a script to look for the non conform files and run dart format —like-length=120 „files location“
0
0
0
RT @FlutterDev: Roses are red, widgets are neat, 3.29 can't be beat 💓 The latest release includes updates to improve developer experience,…
0
120
0
@luke_pighetti Whaat the hell did I just read. It basically validates WWDC motto „SwiftUI is the language of choice for Multi-platform“
0
0
2
@ASalvadorini @drcoderz A more reactive phrasing (e.g., emitNewState(), dispatch(), or updateState()) could better communicate what’s happening under the hood while keeping the simplicity intact. What do u think?
1
0
1
Impressive.
If you're a mobile engineer or interested in iOS and Android, this podcast episode is as good as it gets: How Notion builds its iOS and Android apps. Two of Notion's founding mobile engineers help us dive deep into the productivity app used by tens of millions of users on mobile. Listen to it or watch it here: Spotify: YouTube: Apple: Web & transcript: -- This episode is brought to you by @DeveloperXM the engineering intelligence platform designed by leading researchers. Learn more about them here: (Coincidentally, DX have just launched a very interesting dev productivity framework called DX Core 4: -- Three interesting takeaways from this conversation: 1. Notion’s native mobile team is surprisingly small! Notion employs about 600 staff, but the mobile team is only 11 people – including iOS and Android. This team size is very small, especially considering how Notion serves more than 10M users on both iOS and Android. We’re likely talking about one engineer for every ~2M or more users! 2. Moving from web-based to native was an incremental process by necessity. Thanks to a small native team, and the need to keep the mobile apps up-to-date with the latest Notion features, the native mobile engineering team didn’t have the luxury of doing a large mobile app rewrite. Instead, they did the sensible thing of slowly migrating parts of the app. Today, most of Notion’s apps are fully native, save for the editor. The editor remains one of the most complex parts of Notion. 3. Notion releases their app on a weekly cadence. Native mobile apps need to go through an app review flow from Apple and Google, and so many native apps are released less frequently, to account for this overhead. Notion doing a weekly release cycle is impressive – and it can serve as inspiration for other native mobile teams. If Notion, with 10M+ native users and a small team, does this, other native teams can as well! Thanks to the Notion team for sharing all these details!
0
0
0
@swiftfulthinkng Many devs also have the misconception that UI design patterns are Architecture ones (ex: MVVM, MVC,MVP)
0
0
0