![Jahanzeb Ahmed Khan Profile](https://pbs.twimg.com/profile_images/1813316941081137152/AKCFI6jy_x96.jpg)
Jahanzeb Ahmed Khan
@jahanzeb10
Followers
515
Following
4K
Statuses
4K
Building products with #nocode • https://t.co/1OBjCOoDHv • Might launch a product soon • Amateur Boxer 🥊 Building Checklist - https://t.co/A1XYU4D8Sn
Lahore, Pakistan
Joined May 2010
People who want to start using AI for content creation Use AI to find challenges related to your work Give your take on the approach and just multiply I schedule 1 week's post every weekend Everything else I do randomly throughout the day The best part about it, I don't have to constantly think about content everyday I have 2 posts scheduled daily If you want help with the prompt let me know
0
0
0
Most people fear sharing too much, but holding back leads to you being invisible. Share failures as teachable moments. Talk about processes more than your output Your imperfections are what make you unique Admit what you don’t know, it’s relatable. Building a personal brand isn't about gaining followers, it's about building a community that helps you grow and build trust among each other Authenticity builds brands
0
0
0
Underestimating timeline estimates is one of the biggest issues devs face You scope out a feature with exact deliverables and still end up over shooting the deadline I used to have the most outrageous timeline jumps when I was building @bubble apps and wasn't part of the scoping journey Here's how I fixed it Rule #1 As the dev, always get involved in the scoping process. You can give a lot of input on how to build and structure the feature required, sometimes you'll have to say no Rule #2 Break down the feature in parts Data UI Journey Workflows Rule #3 Always add 25-30% more estimates for bug fixes or any improvements you might have skipped during the scoping phase. Final Rule Always under promise and over deliver & see how your clients react to your work and reliability.
0
0
1
One thing I always do before I start building out any project in @bubble I write down what features we're focusing on, solving one problem at a time. I use the MoSCoW method Must have, should have, could have & won't have Your purpose should be to launch fast and keep iterating as you get feedback Simplicity drives result
6
0
14
Struggling while making mobile responsive designs? I follow the same rules to create pixel perfect responsive builds every time Prioritize responsive design: Design the structure of each page for web and mobile on figma Create a system to add margin and padding (I use 16-24 for web and 8-16 for mobile) Test as you go Test across all devices. Build web first, with mobile layout in mind Simplicity is super important if you want to build an app that's mobile friendly! No need to over complicate things
0
0
1
Reuploading this @bubble tip: Trigger picture uploader using a separate button for better #ux If a picture uploader’s value is pre-filled, users might get confused on how to upload/change the image To create a good experience use this simple JavaScript to trigger the uploader from a separate button Here’s the javascript snippet function clickUploadElement() { document.getElementById("picture-uploader").getElementsByTagName("input")[0].click(); } // function clickUploadElement() Note: Past picture-uploader in your picture uploader’s ID Attribute
1
0
1
The biggest upsell of using #NoCode to build your MVP isn't the price, it's speed. Previously you would have to hire a team of developers to code out your application. This would take months. Today you can launch in weeks Build 5x faster 👉
0
0
0
If you've just started out with @bubble and can't find ideas to build to showcase your skills. Head over to how to build on bubble and pick any app you want to clone. Some of the best ones are Airbnb, Indiehackers & Duolingo Link:
1
0
6
Has anyone in my list been able to publish their @bubble app on the apple store I need to ask some questions
4
0
2
Underestimating timeline estimates is one of the biggest issues devs face You scope out a feature with exact deliverables and still end up over shooting the deadline I used to have the most outrageous timeline jumps when I was building @bubble apps and wasn't part of the scoping journey Here's how I fixed it Rule #1 As the dev, always get involved in the scoping process. You can give a lot of input on how to build and structure the feature required, sometimes you'll have to say no Rule #2 Break down the feature in parts Data UI Journey Workflows Rule #3 Always add 25-30% more estimates for bug fixes or any improvements you might have skipped during the scoping phase. Final Rule Always under promise and over deliver & see how your clients react to your work and reliability.
1
0
0