Mobile Tech
1.14K subscribers
91 photos
8 videos
6 files
138 links
Michael Lazebny's blog about @dart and @flutter
lazebny.io
Download Telegram
Creating reusable UI components + responsive & adaptive design.

Take a look at how Text widgets are implemented and a Window Size Scope. Really love those ones.

https://lazebny.io/ui-components-adaptive-and-responsive-design/
πŸ”₯7
I have implemented authentication for my own app that involved Supabase and Oauth login via Google.

If you’re interested, I will drop full working code when this post reaches 80 thumbs up πŸ‘
πŸ‘99πŸ”₯3❀1πŸ‘Ž1πŸ€“1
Some of my notes for the upcoming article about Navigation in Flutter!
πŸ”₯7πŸ‘2😎2
Learn how to build efficient sticky headers in Flutter using slivers for seamless scrolling. Includes code examples and best practices!

https://lazebny.io/sticky-headers

#flutter #article
πŸ‘9πŸ”₯3
Hi everybody! Hot topic.

I will give a talk about dependency management (injection, initialiazation, delivery) in Flutter!

Time:
05/12/2024 18:00 CET

https://www.youtube.com/live/NiolORe9B4w?si=_10-akEZkmyDhx2A
15πŸ‘9πŸ”₯7
Mobile Tech
On Saturday I will talk about icons https://www.youtube.com/watch?v=cTUU4K4mD0A
My laptop died 😁

I was not very satisfied with the quality of this stream, so I will make a new one in the New Year!
😒8❀‍πŸ”₯1πŸ‘1
Call for ideas!

Please write what you would like to see an article about
❀6πŸ”₯1
Removing factories from sizzle starter. They're adding too much boilerplate.

https://github.com/hawkkiller/sizzle_starter/pull/404
πŸ‘12😁3❀‍πŸ”₯1
Ability to clearly explain your thoughts helps in life a lot. This is especially important when you're working in large teams and need to share your knowledge with others (by writing documentation, code comments, etc.)

These free Technical Writing courses by Google can be a good start:
https://developers.google.com/tech-writing/one
https://developers.google.com/tech-writing/two
https://developers.google.com/style
πŸ‘6πŸ”₯5
Was thinking about using arrow or block functions. In the past I preferred arrow, but noticed that it makes code longer and less readable.

Compare. Which way do you prefer?
πŸ‘6