📌 Model va Entity – farqi nimada?
Ko‘pchilik dasturchilar bu ikki tushunchani chalkashtirib yuboradi. Aslida esa, ular arxitekturaning butunlay boshqa qatlamlariga tegishli!
👨💻 Entity - ma'lumotlar bazasi bilan ishlaydi
🧠 Model - UI va API qatlamida ishlatiladi
✅ Qachon qaysi birini ishlatish kerak?
✅ Mapper funksiyalar qanday yoziladi?
✅ Real Flutter misollar bilan tushuncha oling!
telegram kanalga a'zo bo'ling: @flutter_toolkits
📖 To‘liq maqola: Medium maqolamga o‘tish
#Flutter #CleanArchitecture #Dasturlash #ModelVsEntity
Ko‘pchilik dasturchilar bu ikki tushunchani chalkashtirib yuboradi. Aslida esa, ular arxitekturaning butunlay boshqa qatlamlariga tegishli!
👨💻 Entity - ma'lumotlar bazasi bilan ishlaydi
🧠 Model - UI va API qatlamida ishlatiladi
✅ Qachon qaysi birini ishlatish kerak?
✅ Mapper funksiyalar qanday yoziladi?
✅ Real Flutter misollar bilan tushuncha oling!
telegram kanalga a'zo bo'ling: @flutter_toolkits
📖 To‘liq maqola: Medium maqolamga o‘tish
#Flutter #CleanArchitecture #Dasturlash #ModelVsEntity
Medium
🧩 Model va Entity o‘rtasidagi farq: Dasturchilar uchun batafsil qo‘llanma
# 🧩 Model va Entity o‘rtasidagi farq: Dasturchilar uchun batafsil qo‘llanma
👍1🔥1
For a Flutter developer, the median number of web searches and website visits per day is typically:
🔍 Search Queries
👉 20–60 queries/day — due to:
Widget behaviors (ListView, Column, Stack, etc.)
Package usage (dio, flutter_bloc, go_router, etc.)
Platform-specific issues (iOS/Android quirks)
Build/CI errors
UI/UX customizations
Firebase, notifications, deep linking, etc.
🌐 Websites Visited
👉 10–30 sites/day, often including:
pub.dev (for packages)
Stack Overflow
GitHub (issues, repos)
Flutter docs (https://docs.flutter.dev)
Medium/Dev.to articles
Reddit/Hacker News or forums
YouTube (video tutorials)
Your own project’s repo or team wiki
Even experienced Flutter devs Google common things like flutter container full height, flutter dart format date, or flutter release apk size.
(Source - ChatGPT)
@flutterdevuz
🔍 Search Queries
👉 20–60 queries/day — due to:
Widget behaviors (ListView, Column, Stack, etc.)
Package usage (dio, flutter_bloc, go_router, etc.)
Platform-specific issues (iOS/Android quirks)
Build/CI errors
UI/UX customizations
Firebase, notifications, deep linking, etc.
🌐 Websites Visited
👉 10–30 sites/day, often including:
pub.dev (for packages)
Stack Overflow
GitHub (issues, repos)
Flutter docs (https://docs.flutter.dev)
Medium/Dev.to articles
Reddit/Hacker News or forums
YouTube (video tutorials)
Your own project’s repo or team wiki
Even experienced Flutter devs Google common things like flutter container full height, flutter dart format date, or flutter release apk size.
(Source - ChatGPT)
@flutterdevuz
docs.flutter.dev
Flutter documentation
Get started with Flutter. Widgets, examples, updates, and API docs to help you write your first Flutter app.
Forwarded from Sabohat K | Tech blog 🇵🇸 (Sabohat)
Why Your App Feels Slow: The Top 4 Performance Killers
1) Network Latency & API Efficiency – Slow server responses or too many API calls make the app feel laggy.
2) Data Access & Storage Optimization – Poor database queries or repeated data fetches slow down performance.
3) Algorithm & Logic Efficiency – Inefficient code leads to delays, especially with large datasets or complex operations.
4) UI Rendering & Front-End Performance – Heavy rendering, unoptimized images, or layout shifts hurt responsiveness.
*The list items are prioritized in the order of impact
1) Network Latency & API Efficiency – Slow server responses or too many API calls make the app feel laggy.
2) Data Access & Storage Optimization – Poor database queries or repeated data fetches slow down performance.
3) Algorithm & Logic Efficiency – Inefficient code leads to delays, especially with large datasets or complex operations.
4) UI Rendering & Front-End Performance – Heavy rendering, unoptimized images, or layout shifts hurt responsiveness.
*The list items are prioritized in the order of impact
Milliy va ishonchli tizim: DON
"DON" qanday ishlaydi?
Yig'ilgan DON lar evaziga:
🏅 2 xonali kvartira
🏅 2 ta GENTRA
🏅 43 dyumlik 10 ta televizor...
... va ko'plab boshqa sovrinlarni yutib olishingiz mumkin.
Havolani bosing va DON yig'ishni boshlang:
BOSHLASH
@flutterdevuz
"DON" qanday ishlaydi?
- Sizga kunlik vazifalar beriladi, ularni bajarish evaziga mukofot sifatida DON taqdim qilinadi;
- Vazifalar turiga qarab yoki ko‘proq yoki kamroq DON taqdim qilinadi;
- DON qanchalik ko‘p bo‘lsa ularni sarflab yutuqli o‘yinda ishtirok etishingiz mumkin;
- DON ga har kunlik tashrif orqali ham DON mukofotlarini olishingiz mumkin va bu mukofotlar bir muddat o‘sib boradi;
Yig'ilgan DON lar evaziga:
🏅 2 xonali kvartira
🏅 2 ta GENTRA
🏅 43 dyumlik 10 ta televizor...
... va ko'plab boshqa sovrinlarni yutib olishingiz mumkin.
Havolani bosing va DON yig'ishni boshlang:
BOSHLASH
@flutterdevuz
⚡1👍1
Odatiy xodimlikdan texnologik biznes egasiga aylanish uchun sodda yo'l xaritasi:
1. Maqsadingizni aniqlang
O‘zingizga savol bering:
- Men o‘z mahsulotimni yaratmoqchimanmi? (masalan: mobil ilova, veb-sayt, SaaS)
- Yoki frilans, startap, xizmat ko‘rsatish agentligi ochmoqchimanmi?
- Yoki mavjud bozor muammosini texnologik yechim bilan hal qilmoqchimanmi?
Aniq maqsad – aniq harakatlarni paydo qiladi.
2. Muammo toping – g‘oya shu yerda ana o'sha yerda yashiringan bo'ladi
Texnologik biznes g‘oyadan emas, muammoni topishdan boshlanadi:
- Ishingizda yoki kundalik hayotingizda qanday muammolar bor?
- Odamlar nimadan norozi? Nega vaqt yoki pul yo‘qotishyapti?
- Bu muammoni hal qilish uchun qancha pul to‘lashmoqda?
Yaxshi g‘oya – bu hal qilinmagan muammoga yaxshi yechim hisoblanadi.
3. Ishlayotganingizda tayyorgarlik ko‘ring
Ishingizni biznesni boshlash uchun trampilin sifatida ko‘ring:
- Pul jamg‘aring (kamida 6-12 oylik xarajatlaringizga yetadigan)
- Tajriba oling (texnik ko‘nikmalar, loyiha yuritish, mijozlar bilan ishlash)
- Ilk mijoz yoki foydalanuvchini ishxonadayoq toping (shu muammo sizni o‘rab turgan muhitda bormi?)
4. Kichik loyiha yoki VMVP tayyorlang
Ilk bosqichda to‘liq mahsulot emas, minimum ishlaydigan mahsulot (MVP) yarating:
- Oddiy veb-sayt, Telegram bot, Google form, Notion sahifa ham bo‘lishi mumkin
- Maqsad: ilovangiz yoki xizmatingiz foydalimi yoki yo‘qmi, sinab ko‘rish
5. Foydalanuvchi/Mijoz to‘plashni o‘rganing
Texnologik biznes = texnologiya + mijoz. Har doim quyidagilarga e’tibor qarating:
- Qayerdan foydalanuvchi topasiz?
- Qanday qilib ularga xizmat yoki mahsulotingizni tushuntirasiz?
- Ular sizga to‘laydimi?
6. Parallel ravishda daromad topishni boshlang
Asosiy ishda ishlab turgan holda:
- Konsultatsiya
- Kichik ilova yoki bot orqali passiv daromad
*Frilans xizmatlar tavsiya etilmaydi!
Daromad kira boshlaganda ishdan chiqish uchun qulay fursat keladi. Bunda o'z ishxonangizni oldindan ogohlantirish tavsiya etiladi.
7. To‘liq o‘z biznesingizga o‘ting, to'liq!
Quyidagilar mavjud bo‘lsa, ishni tashlab o‘z yo‘lingizga o‘ting:
- Kamida 6 oy yashashga yetadigan jamg‘arma
- Ishlaydigan biznes model
- Barqaror mijozlar/foydalanuvchilar oqimi
- O‘z ustingizda ishlashga tayyorlik (sabab: endi hamma javobgarlik sizda)
Agar yuqoridagilardan bittasi sizda yo'qligini sezsangiz, iltimos qayta o'ylab ko'ring. O'zbekiston sharoitida yana bir zo'r imkoniyat bor. Bu sherikchilik, hozir ishlab turgan joyingizga hech bo'lmaganda 1% sherik bo'lish imkoniyati borligini tekshiring agar bo'lsa kompaniya ulushdori bo'ling, chunki yuqoridagi 7ta ko'rsatilgan talablar odatda kamida 10+ yil tajribaga egalarda uchrashi mumkin, bu degani 100% kafolat degani emas. Shu sababdan xizmat ko'rsatish sohasida imkon qadar o'z korxonanggizda bosh qaror qabul qiluvchilar qatoriga o'tish uchun harakat qiling.
Agar gap startap haqida ketayot bo'lsa, unga alohida keyingi postlarda to'xtalamiz.
Do'stlarga ulashing, ko'proq odamga manfaatli bo'lishi uchun harakatdaman - @AlisherAhmatovich
1. Maqsadingizni aniqlang
O‘zingizga savol bering:
- Men o‘z mahsulotimni yaratmoqchimanmi? (masalan: mobil ilova, veb-sayt, SaaS)
- Yoki frilans, startap, xizmat ko‘rsatish agentligi ochmoqchimanmi?
- Yoki mavjud bozor muammosini texnologik yechim bilan hal qilmoqchimanmi?
Aniq maqsad – aniq harakatlarni paydo qiladi.
2. Muammo toping – g‘oya shu yerda ana o'sha yerda yashiringan bo'ladi
Texnologik biznes g‘oyadan emas, muammoni topishdan boshlanadi:
- Ishingizda yoki kundalik hayotingizda qanday muammolar bor?
- Odamlar nimadan norozi? Nega vaqt yoki pul yo‘qotishyapti?
- Bu muammoni hal qilish uchun qancha pul to‘lashmoqda?
Yaxshi g‘oya – bu hal qilinmagan muammoga yaxshi yechim hisoblanadi.
3. Ishlayotganingizda tayyorgarlik ko‘ring
Ishingizni biznesni boshlash uchun trampilin sifatida ko‘ring:
- Pul jamg‘aring (kamida 6-12 oylik xarajatlaringizga yetadigan)
- Tajriba oling (texnik ko‘nikmalar, loyiha yuritish, mijozlar bilan ishlash)
- Ilk mijoz yoki foydalanuvchini ishxonadayoq toping (shu muammo sizni o‘rab turgan muhitda bormi?)
4. Kichik loyiha yoki VMVP tayyorlang
Ilk bosqichda to‘liq mahsulot emas, minimum ishlaydigan mahsulot (MVP) yarating:
- Oddiy veb-sayt, Telegram bot, Google form, Notion sahifa ham bo‘lishi mumkin
- Maqsad: ilovangiz yoki xizmatingiz foydalimi yoki yo‘qmi, sinab ko‘rish
5. Foydalanuvchi/Mijoz to‘plashni o‘rganing
Texnologik biznes = texnologiya + mijoz. Har doim quyidagilarga e’tibor qarating:
- Qayerdan foydalanuvchi topasiz?
- Qanday qilib ularga xizmat yoki mahsulotingizni tushuntirasiz?
- Ular sizga to‘laydimi?
6. Parallel ravishda daromad topishni boshlang
Asosiy ishda ishlab turgan holda:
- Konsultatsiya
- Kichik ilova yoki bot orqali passiv daromad
*Frilans xizmatlar tavsiya etilmaydi!
Daromad kira boshlaganda ishdan chiqish uchun qulay fursat keladi. Bunda o'z ishxonangizni oldindan ogohlantirish tavsiya etiladi.
7. To‘liq o‘z biznesingizga o‘ting, to'liq!
Quyidagilar mavjud bo‘lsa, ishni tashlab o‘z yo‘lingizga o‘ting:
- Kamida 6 oy yashashga yetadigan jamg‘arma
- Ishlaydigan biznes model
- Barqaror mijozlar/foydalanuvchilar oqimi
- O‘z ustingizda ishlashga tayyorlik (sabab: endi hamma javobgarlik sizda)
Agar yuqoridagilardan bittasi sizda yo'qligini sezsangiz, iltimos qayta o'ylab ko'ring. O'zbekiston sharoitida yana bir zo'r imkoniyat bor. Bu sherikchilik, hozir ishlab turgan joyingizga hech bo'lmaganda 1% sherik bo'lish imkoniyati borligini tekshiring agar bo'lsa kompaniya ulushdori bo'ling, chunki yuqoridagi 7ta ko'rsatilgan talablar odatda kamida 10+ yil tajribaga egalarda uchrashi mumkin, bu degani 100% kafolat degani emas. Shu sababdan xizmat ko'rsatish sohasida imkon qadar o'z korxonanggizda bosh qaror qabul qiluvchilar qatoriga o'tish uchun harakat qiling.
Agar gap startap haqida ketayot bo'lsa, unga alohida keyingi postlarda to'xtalamiz.
👍1👏1
Forwarded from Hacking for trolls
kocha-lang.uz kecha @shakhzodme aytgan til :)
Forwarded from Techie's Blog
#useful
🐙 Trending Repository: tdesign-flutter ⭐811
A Flutter UI components lib for TDesign. See components here
🐙 Trending Repository: tdesign-flutter ⭐811
A Flutter UI components lib for TDesign. See components here
Forwarded from Techie's Blog
Assalomu alekum hammaga.
go_router ishlatuvchilarni .popUntil() funksyaning yetishmasligi ko'pchilikni qiynasa kerak. Buning uchun yechim sifatida qulay extension yozdim balki foydasi tegib qolar:
go_router contextga bog'langani uchun unga ham qoshimcha yozib qo'yamiz:
p.s/ Boshqacha yechimlar bo'lsa albatta kutib qolaman.
go_router ishlatuvchilarni .popUntil() funksyaning yetishmasligi ko'pchilikni qiynasa kerak. Buning uchun yechim sifatida qulay extension yozdim balki foydasi tegib qolar:
extension GoRouterExtension on GoRouter {
void popUntilPath(String ancestorPath) {
while (routerDelegate.currentConfiguration.matches.last.matchedLocation != ancestorPath) {
if (!canPop()) {
return;
}
pop();
}
}
}
go_router contextga bog'langani uchun unga ham qoshimcha yozib qo'yamiz:
extension BuildContextExtensions on BuildContext {
void popUntil(String targetRoute) {
final router = GoRouter.of(this);
router.popUntilPath(targetRoute);
}
}
p.s/ Boshqacha yechimlar bo'lsa albatta kutib qolaman.
Tarmoqlarda iOS 26 dan "Liquid Glass" UI prinspida ishlashini aytib, Flutter (yoki krossplatformachilar) buni eplolmaydi deb "vahima" qilisha boshlaganida men:
😁3
UzPay peketi yangilandi, endi siz QR kod ham generatsiya qila olasiz,
https://pub.dev/packages/uzpay
@flutterdevuz
https://pub.dev/packages/uzpay
@flutterdevuz
🔥5⚡1
Forwarded from Samandar Ahadjonov
#tajribadan
Biron muaommo ustida idealdagi backendchi va frontendchi o'rtasidagi meeting uzog'i 1-2 daqiqa davom etishi kerak. Bundan ko'p vaqt ketdimi, demak orada kimdir noprofessional.
Dialog taxminan bunaqa bo'lishi kerak:
Front: Bunaqa-bunaqa muammo bor, mana bunaqa qilsak bo'ladimi?
Back: Ha bo'ladi / Yo'q, lekin bunaqa qilsak bo'ladi.
Front: Bo'ldi kelishdik, rahmat.
Professionallar ichida "U edi - bu edi" degan "adi-badi" bo'lmaydi.
@ahadjonovss
Biron muaommo ustida idealdagi backendchi va frontendchi o'rtasidagi meeting uzog'i 1-2 daqiqa davom etishi kerak. Bundan ko'p vaqt ketdimi, demak orada kimdir noprofessional.
Dialog taxminan bunaqa bo'lishi kerak:
Front: Bunaqa-bunaqa muammo bor, mana bunaqa qilsak bo'ladimi?
Back: Ha bo'ladi / Yo'q, lekin bunaqa qilsak bo'ladi.
Front: Bo'ldi kelishdik, rahmat.
Professionallar ichida "U edi - bu edi" degan "adi-badi" bo'lmaydi.
@ahadjonovss
👍5
Dasturchilarni qanday jahlini chiqarish mumkin yoki yangi rahbarlarga qo'llanma
- Demo vaqtida "men buni AI yordamida 5 daqiqada qilaman" deb ayting.
- Dasturchiga yangi topshiriq bering, agar hozir boshqa bir ish bilan bandligini aytsa, usha ishni AI`ga berib, o'zi yangi topshiriq bilan shug'ullanishi kerakligini ayting.
- Boshqa bo'limlarni yig'ilishlariga dasturchilarni taklif qiling.
- Ish guruh chatiga boshqa IT tashkilotlar xodimlarni bo'shatib, o'rniga AIdan foydalanishni boshlaganliklari haqidagi yangiliklarni tashlab turing.
- Prodga chiqishdan bir soat oldin “Men bitta kichkina o‘zgarish kiritdim” deb xabar bering.
- Kodni refactor qilishga qo'ymang, buni bekorchilikdan qilinadigan ish deb ayting.
- Tez tez AI`dan unumli foydalanmayapsizlar deb aytib turing.
- Githubga kirib, biror bir kodni olib AI`dan review qilishini so'rang, keyin javobni dasturchilar guruhida tashlang.
- Bu narsa qiyin deyishsa, "Bilgan odamga, bitta promptda" deb ayting.
- Fikringizni tez tez o'zgartirib turing va loyihani shunga moslab o'zgartirish kerakligini ayting.
- Oylikni dasturchilar yozgan kod hajmiga qarab to'lang.
@flutterdevuz
- Demo vaqtida "men buni AI yordamida 5 daqiqada qilaman" deb ayting.
- Dasturchiga yangi topshiriq bering, agar hozir boshqa bir ish bilan bandligini aytsa, usha ishni AI`ga berib, o'zi yangi topshiriq bilan shug'ullanishi kerakligini ayting.
- Boshqa bo'limlarni yig'ilishlariga dasturchilarni taklif qiling.
- Ish guruh chatiga boshqa IT tashkilotlar xodimlarni bo'shatib, o'rniga AIdan foydalanishni boshlaganliklari haqidagi yangiliklarni tashlab turing.
- Prodga chiqishdan bir soat oldin “Men bitta kichkina o‘zgarish kiritdim” deb xabar bering.
- Kodni refactor qilishga qo'ymang, buni bekorchilikdan qilinadigan ish deb ayting.
- Tez tez AI`dan unumli foydalanmayapsizlar deb aytib turing.
- Githubga kirib, biror bir kodni olib AI`dan review qilishini so'rang, keyin javobni dasturchilar guruhida tashlang.
- Bu narsa qiyin deyishsa, "Bilgan odamga, bitta promptda" deb ayting.
- Fikringizni tez tez o'zgartirib turing va loyihani shunga moslab o'zgartirish kerakligini ayting.
- Oylikni dasturchilar yozgan kod hajmiga qarab to'lang.
@flutterdevuz
😁2🆒1
Media is too big
VIEW IN TELEGRAM
⚡2😱2👍1👌1
Forwarded from Techie's Blog
Vanihoyat meaningful move.
Oldinlari faqat inspector ichidan boshqarilar edi manashu "zormonda". Endi deviceni o'ziga qo'shib yaxshi ish qilishibdi
Oldinlari faqat inspector ichidan boshqarilar edi manashu "zormonda". Endi deviceni o'ziga qo'shib yaxshi ish qilishibdi
Most Advanced and Useful Flutter Techniques (from r/FlutterDev)
### Advanced Flutter Techniques
- **State Management**
- Use tools like Riverpod for clean and easy async state management.
- Build async-friendly UI components that react to AsyncValue states.
- **Performance Optimization**
- Profile your app regularly.
- Follow good architectural patterns to reduce the need for later optimization.
- **Custom Animations and Transitions**
- Use the `flutter_animate` package.
- Use the Hero widget for smooth page transitions.
- **Native Platform Integration**
- Use PlatformView and MethodChannel to work with native SDKs.
- Call C/C++ libraries via Dart FFI (e.g., OpenCV for image processing).
- Try Flutter Rust Bridge and other emerging FFI tools.
- **Effective Debugging**
- Use breakpoints and verify app state during debugging.
- **CI/CD Pipelines**
- Use Melos for monorepo management, running tests, and scripting both locally and in CI.
- **Complex UI and Layouts**
- Use basic Flutter widgets like MediaQuery, LayoutBuilder, and SafeArea for responsive design.
- **Best Testing Practices**
- Write composable helper functions inspired by React Hooks to manage lifecycle and resources in tests, reducing boilerplate.
- **Working with Packages & Plugins**
- Use Melos to manage multiple packages and streamline your workflow.
- **Other Useful Practices**
- Follow SOLID design principles for maintainable code.
- Use git hooks to automate formatting and other common tasks.
- Launch emulators from the terminal or VSCode launch.json for faster startup.
- Set up centralized logging with strategy patterns for analytics and console logs.
- Create strongly-typed network libraries with mock implementations for easier testing.
### Use Cases for Native Code Integration
- Alarm screen that appears even when the app is closed or the phone is locked.
- Native APIs or libraries not yet available in Flutter (e.g., Azure Speech Recognition).
- Heavy processing tasks using C++ libraries via Dart FFI (e.g., OpenCV).
@flutterdevuz