Welcome to the September 2025 edition of the #PowerAppsPulse, our monthly series where we highlight the latest incremental improvements! 🎉    In this episode, Elaiza Benitez dives into several updates for Canvas apps and Plan Designer, including:   - Maximum width and height properties for controls in responsive containers - Improvement to renaming controls in tree view - Variables sorted alphabetically within their categories - New reasoning blob for makers to view the detailed reasoning behind Copilot decision in suggesting apps, flows and agents From new features to performance improvements, we’ve got everything you need to stay up-to-date and make the most out of #PowerApps. Stay tuned as we explore these updates and show you how they can enhance your app-building journey.    Click the link below to see what else is new this month! https://lnkd.in/dH_dZgPN

Work directly with Steve Huynh to get a high performance review and your next tech promotion in a year, guaranteed! https://lnkd.in/gD8bEf2H The Future of IDEs: Orchestration Over Creation  "Terminal-based apps are getting fancy UI features - they'll bust out at some point. It's an IDE around orchestration and review, not code creation."  Be careful which models and tools you tie yourself to. Things are changing so fast that decisions that seem good can turn upside down in six months.  Full episode: https://lnkd.in/gvNYW8Jv

3 Lessons Every Builder Can Learn From The Mom Test One of the biggest mistakes founders and product managers make is asking the wrong questions. In The Mom Test by Rob Fitzpatrick, we learn that people, especially friends, family, and even customers, often lie to protect your feelings (not intentionally!). Here are 3 key lessons every builder should know 👇 1️⃣ Don’t ask for opinions, ask about behavior. Instead of “Would you use this app?” ask “How do you currently solve this problem?” 2️⃣ Stop pitching, start listening. The goal isn’t to sell your idea, it’s to understand your user’s pain deeply. 3️⃣ Good questions reveal truth, bad ones confirm bias. Ask questions that make you uncomfortable, that’s where the real insight lives. So before you build your next product, ask better questions. That’s how you find truth before wasting time, money, and energy. 💡 At The Proddly Community (TPC), we learn, build, and grow together as product creators. Join our community to connect with like minds, share your ideas, and build smarter. 👉 Join The Proddly Community today: https://lnkd.in/dJT-6zJZ #ProddlyCommunity #ProductManagement #TheMomTest #BuildersMindset #StartupGrowth #IdeaValidation

💭 “Empty state” – The most forgotten screen but the one that says the most. 💡 “Empty state” happens when users interact with an app but nothing appears – no data, no result, no clue. Yet, it’s one of the most overlooked moments in product design. Every “empty” screen is actually a chance to communicate. If your message just says “No data available”, users hit a dead end. But if it says “Try adjusting your filters to see more results”, you’re guiding them. And when written with brand personality, like: Duolingo’s “Your streak could start today🔥” on an empty screen. You’re turning a pause into purpose.💛 🚀 A thoughtful empty state turns silence into connection and keeps users engaged, even when there’s nothing to see! #HeySheep #UIUX #ProductDesign #UserExperience

What makes us truly love a product, not just use it? I recently discovered a design framework that explores how joy and surprise can transform functional solutions into experiences that people deeply connect with. It’s the Delight Model by Nesrine Changuel, PhD ✨ Her approach focuses on identifying people’s motivators, turning them into product opportunities, and categorizing them into three levels of delight: surface, low, and deep. Delight = Joy + Surprise + (Functional Need + Emotional Need) This idea made me revisit "Future Heroes", a gamified social-emotional learning app for primary school kids that I designed a while ago. Looking back, I realized we were missing the deep delight, that powerful intersection where functional and emotional needs truly merge for kids. That’s when I added the “Character Call” feature. The day after failing a mission (for example), the character calls the kid to ask genuine questions. ”Hey, did something not go the way you hoped yesterday? Want to know what I do when things get frustrating?” It might transform the app from a tool kids use to a companion that genuinely connects with them. What's a product that's really delighted you recently, something that just worked perfectly and made you feel good using it? ✨ #productdesign #delightdesign #userexperience

𝐈’𝐯𝐞 𝐚𝐥𝐰𝐚𝐲𝐬 𝐛𝐞𝐥𝐢𝐞𝐯𝐞𝐝 𝐭𝐡𝐚𝐭 𝐰𝐡𝐢𝐭𝐞𝐛𝐨𝐚𝐫𝐝𝐬 𝐛𝐮𝐢𝐥𝐝 𝐛𝐞𝐭𝐭𝐞𝐫 𝐢𝐝𝐞𝐚𝐬 𝐭𝐡𝐚𝐧 𝐏𝐨𝐰𝐞𝐫𝐏𝐨𝐢𝐧𝐭 𝐨𝐫 𝐚𝐧𝐲 𝐟𝐚𝐧𝐜𝐲 𝐭𝐨𝐨𝐥𝐬. Because when you’re at the board, you can’t hide behind pretty slides — you have to think. This sketch was from our early brainstorming sessions — when we were working on the early days of the Hajiri App. We were trying to decode how a site manager sees his day — numbers, costs, people. It wasn’t about UI, it was about the use case. Good products don’t come from tools. They come from honest conversations and a marker. #ProductThinking #ConstructionTech #Innovation #Leadership #HajariApp

You need to send a big PPT deck to your boss — but also buy socks for your kid. Miss one, and tomorrow’s a mess. That’s real life — and that’s where tickit started. Just add, tick, and feel that small win. A simple reminder app for small daily wins in work and life — even if it takes three coffees to start the day. I led the ideation, prototyping, and branding — proves that learning never stops when you stay curious and keep building. Current tools in the markets are great for previews and feedback, but the next frontier is clear: seamless, creator- and producer-led product deployment from Figma to full app. #genAIcreative #seamlessdeploy

Accessibility can feel like a mountain to climb for any team, right? But there's ONE powerful, often overlooked aspect that can dramatically speed up fixes and improve user experience for everyone! There are awesome tools out there – Chrome extensions, other utilities that give you a high-level view of your app's current a11y state for the page you are focused on. But they often miss the big picture and don't help you tackle the root issues faster. The key to truly improving that user experience? Addressing accessibility at the component level. Think of components as the building blocks of your UI. If you get the accessibility right at this foundational layer, it cascades much faster throughout your entire application. You're fixing the root problem, not just patching symptoms! And this is where Storybook truly shines! You're already building your UI in pieces, right? Storybook gives you an isolated environment to build, test, and piece them together. This means you can test all the accessibility at the component layer itself! When a violation pops up, you know exactly where to fix it. Even better? Chromatic automates all of this, giving you a complete, up-to-the-minute snapshot of your accessibility status across all your work. That’s what’s super exciting for me! Empowering engineers to build more inclusively, more confidently, and faster! 🎉🎉🎉 #a11y #accessibility #storybook #storybookjs #webdevelopment #uitesting #chromatic

𝗧𝗵𝗶𝘀 𝗪𝗲𝗲𝗸 𝗮𝘁 𝗥𝗼𝗹𝗲𝗲𝗳𝘆 👩🏻💻✅ I’ve added 𝙞𝙣𝙩𝙚𝙧𝙖𝙘𝙩𝙞𝙫𝙚 𝙛𝙚𝙚𝙙𝙗𝙖𝙘𝙠 𝙛𝙤𝙧𝙢𝙨 that can be used live during a roleplay. They let participants give each other focused, structured feedback with clear variables and choices — and at the end, you get a summary you can keep for your notes. I’ve also made 𝙨𝙚𝙫𝙚𝙧𝙖𝙡 𝙙𝙚𝙨𝙞𝙜𝙣 𝙞𝙢𝙥𝙧𝙤𝙫𝙚𝙢𝙚𝙣𝙩𝙨 across the app to make everything feel cleaner and more intuitive. 𝗥𝗲𝘀𝘂𝗹𝘁: a more useful, 𝙝𝙪𝙢𝙖𝙣-𝙛𝙞𝙧𝙨𝙩 𝙥𝙧𝙖𝙘𝙩𝙞𝙘𝙚 𝙚𝙭𝙥𝙚𝙧𝙞𝙚𝙣𝙘𝙚 where feedback becomes part of the learning, not an afterthought. #Roleefy #BuildingInPublic #MedicalEnglish #HealthcareCommunication #CALMFramework #StartupJourney

How can you build product intuition, even if you haven’t worked as a PM? You just need to start observing like a PM. Here’s how: 1. Pick any app you use daily Open it with fresh eyes. 2. Ask yourself: • What’s the main action this app wants from me? • What friction do I feel while using it? • What trade-offs do I notice in the design? 3. Watch your behavior Did you skip a step? Close a popup? Abandon mid-way? 4. Write down 3 things: • What worked? • What didn’t? • What you’d test next? That’s it. Do this for 10 apps in 10 days, and you’ll start seeing what most users miss. That’s product intuition. And you don’t need a job title to build it. Save, Share & Repost for those who need this. And if you want to learn more, let’s talk: https://lnkd.in/gW6bFj3n