Bhai aap ny Flutter kese sikha

Bhai aap ny Flutter kese sikha — yeh sawaal mujhse kai baar pucha gaya hai.

Aaj honestly bata deta hun.

Seedhi baat karta hun. Maine Flutter sikhne ke liye koi special course nahi kiya. Koi bootcamp nahi. Koi structured plan nahi tha.

Mere paas already C++, C#, HTML, CSS, JavaScript, PHP, Python ka background tha. Toh Flutter ek nayi language ki tarah nahi thi — ek nayi duniya thi jisme samajhna tha ke cheezein kaise chalti hain.

Maine 2-3 full-length videos dekhe. Har ek 1 hour se zyada ki. Lekin goal yeh nahi tha ke sab yaad ho jaye. Goal sirf yeh tha ke flow samajh aaye. Components kya hain, cheezein kaise connect hoti hain. Bas.

Phir maine project shuru kar diya.

Aur yahan se asli story shuru hoti hai.

Pehla hafte — setup. Sirf setup.

Dependencies download hoti thi. Ghanton tak. Mere paas 4Mbps connection hai — ek typical Pakistani developer ki tarah - shayd kch zyada. Ek cheez download hoti, kuch aur missing hota, phir kch aur, phir kch aur.

7 din. Sirf aik default Flutter app ko screen par lanay k liay lagay.

Demotivating tha. Draining tha. Lekin maine ek cheez ki — har baar kuch fix kiya, aur aage badh gaya. Rukna option nahi tha.

Pehla app actually Iqra ka prototype nahi tha. Sirf woh default code tha jo Flutter automatically generate karta hai. Counter wala. Lekin us din ki feeling alag thi.

Phir step by step.

Pehle emulator par app chali. Phir ek screen update ki — basic si. Phir APK banayi. Phone par install ki. Test ki.

Har step chhota tha. Lekin har step real tha.

Aur tab maine actually Flutter ke liye jo seekhna tha — woh seekha. Mere zehan mein ek solution tha. Ek problem thi jo main khud face kar raha tha. Maine us solution ko banana shuru kar diya.

Coding mostly AI se karwayi. Claude ko mainly use kiya.

Lekin yahan ek important baat hai.

AI ek gaadi hai, aap driver ho.

Jab clearly bata'o ke kya chahiye, exact scenario kya hai, input kya hai — tab sahi result milta hai. Vague sawaal, vague jawab.

Aur kai baar jab code paste karta tha aur integrate nahi hota tha — tab main wapas jaata tha. Concept samajhta tha. Widget kya hoti hai? State kaise kaam karti hai? Phir wapas aata tha.

Yeh "wapas jaana" — yahi actual learning thi.

300 din ho gaye hain is product ko banate hue. Break ke baad adjust karo toh 220-250 real days. Har roz code nahi kiya — marketing bhi hoti thi. Lekin roughly 70% days coding ki.

Aur Flutter ke ilawa jo seekha woh yeh tha:

Brand kaise banayen? Marketing kaise sochen? Customer ke baare mein kaise sochen? Likhna. Content banana. Apna kaam share karna.

Flutter toh ek tool tha. Asal maqsad kuch aur tha.

Toh agar aap Flutter seekhna chahte ho — yeh mera jawab hai:

Pehle flow samjho. Videos se, briefly. Phir kuch banana shuru karo — kuch jo aap actually banana chahte ho. Setup todega. Code nahi chalega. AI bhi kabhi kabhi confuse karega.

Lekin bas fix karte raho. Aur aage badhte raho.

Comments

Earning after the advent of AI, the 3 paths and things that matter

I have received this question more times than I can count. Are jobs gone? Is AI taking over everything? Why are internships not coming through? What do I do with my degree or my skill? Here is my honest answer — not a motivational one. AI has made things easier, and harder at the same time. Because AI can now do multiple things, the person who knows how to get the right things done from AI is preferred over the one who does not. That is the new baseline. Learn the basics of AI regardless of which path you choose — not to become an AI engineer, but to use it well in whatever you are doing. Beyond that, I see three paths. Each one has its own direction. The mistake most people make is not choosing one and going deep on it. Path 1: Build a Personal Product This is the path I am on. I will be honest about where my experience ends. Start by finding a problem — ideally one you personally face. That is your built-in validation. If you have the problem, others likely do too....

A user found the bug I should have caught myself

I was collecting user feedback on Iqra a few weeks ago. One of the users pointed out a bug. A section of the app was not working correctly. I knew the section. I had made changes to it recently — and shipped them directly to production without running through my usual testing flow. A user told me about the bug. Not my emulator. Not my test release. A user. I fixed the bug, made a few more improvements, added some things to the app. When I finally sat down to build the test release properly, this came back to me. So here it is — written down, for anyone building a product right now. The flow that actually protects you Every change, no matter how small, goes through three stages before it reaches your users. First, test on the emulator. Catch the obvious breaks early, before anything leaves your machine. Second, publish a test release and run it on a real device. The emulator lies sometimes — screen sizes behave differently, performance feels different, interactions that ...

How an AI Student is Earning from LinkedIn — and What I Learned from a 17-Minute Call

A few days ago I saw a post on Facebook. Someone sharing that he had started learning AI, done some projects, and was now earning from it. I asked him how. He said he got a client through LinkedIn. I asked him to elaborate. He said let's talk. Seventeen minutes on WhatsApp. That was the whole conversation. But it connected more dots than months of reading about "the opportunity in AI." The problem with how most people learn AI AI is a wide field. Machine learning. Deep learning. Model development. Model deployment. Data analysis. Data analytics. Automation. Most people learning AI are aware of all of these — and that awareness becomes the problem. They keep exploring, keep switching, keep adding things to the list. A year passes and they are still learning. He told me something simple: to stand out and to get clients, you have to focus on one thing. His one thing is RAG — Retrieval Augmented Generation. Not AI in general. Not even a broad category within AI...

Shaukat Ali

Search This Blog