Featured Issues

Mobile development blogs, tutorials and resources inside!Latest Mobile Dev Insights: iOS, Android, Cross-PlatformAdvertise with Us|Sign Up to the NewsletterMobilePro #204: AI in Figma, AI Coding agents in Xcode, Kotlin’s new release, and more…Hi ,Welcome to the 204th edition of MobilePro.You must have noticed the abbreviation AI twice in the headline. It's something you see everywhere now, isn't it? One could say AI arrived in mobile development with a bang, but I'd wager it's arriving quietly, tool by tool, feature by feature, and suddenly, our workflows are going to look completely different.Let that headline tell you the story: First, Apple is bringing AI coding agents directly into Xcode, and then iOS 26.4 could push Siri toward deeper, more app-aware actions. Even on the research side, Apple-backed models are exploring things like generating sound and speech from silent video. AI is no longer a separate thing but an intrinsic part of the default developer toolkit.This makes the design stage an especially important place to slow down and get things right. Because before AI helps you write code faster or analyze metrics better, it can help you think more clearly about what you’re building. That’s why today’s tutorial focuses on speeding up your flow with AI in Figma. If you think this is about automating design, it isn't really that. We're focused largely on removing the friction that shows up early, stuff like fuzzy personas, hidden assumptions, slow iteration, and messy handoffs. Used well, AI in Figma helps teams reach clarity sooner, so everything that follows—code, testing, and iteration—has a much better foundation.Let’s get started!The Problem with One-Size-Fits-All Mobile App Security and How to Fix ItIs your team struggling to balance security requirements with user experience?Join us onFebruary 24at4 PM CET/10 AM ETfor a webinar discussing how leading financial services teams are shifting to data-driven, risk-based mobile security for more precise responses.Register NowSpeeding up your flow with AI in FigmaAI isn’t here to replace designers, and it definitely isn’t here to “auto-design” products. What it is good at is removing the slow, repetitive, and messy parts of modern mobile workflows, the parts that delay alignment, slow down iteration, and create avoidable confusion between design and development.For mobile teams, speed isn’t just about moving fast. It’s about reaching clarity earlier: clearer user assumptions, clearer flows, clearer states, and fewer surprises during implementation.Used well, AI becomes a workflow accelerator for both designers and mobile developers. Designers explore faster without losing intent. Developers get clearer prototypes, more predictable behavior, and fewer handoff translation errors.The goal isn’t to “design with AI.” The goal is to ship better mobile experiences with fewer bottlenecks.Before Figma: faster exploration without false certaintyBefore anyone opens Figma, most projects begin in ambiguity. You’re collecting inputs, forming hypotheses, and trying to understand what the product should be, all while stakeholders expect early direction.This stage is where AI can help most, as long as it isn’t treated as truth.Personas (as scaffolding, not research)AI can quickly generate persona skeletons from early notes, workshop inputs, or stakeholder assumptions. Tools like FigJam’s AI can cluster messy ideas into themes and draft rough persona profiles based on what’s already on the board.External tools like ChatGPT can go further: refining motivations, expanding behaviors, and generating multiple persona variants to explore.The key is to treat personas here as temporary structure, not “validated users.” They’re placeholders that help teams align early and move forward with intention, without pretending the answers are final.Early assumptions (made visible, not buried)Mobile teams often lose time because assumptions stay implicit. AI can help pull those assumptions into the open:What problem are we really solving?What are we assuming about user behavior?What constraints are we ignoring?What’s unclear in the flow?This kind of exploration creates better design conversations, and better developer questions, earlier in the process.Competitive scanning (faster context, less guesswork)Competitive analysis is time-consuming, and it’s often done poorly because it’s rushed. AI tools can help you scan faster and structure insights more cleanly.Source-based tools like Perplexity are especially useful here because they allow you to explore market patterns and product positioning while staying grounded in references. Instead of spending hours collecting fragmented information, you can quickly identify:How similar apps structure key flows?Which patterns are becoming standard?What gaps exist in feature sets or UX expectations?AI as exploration, not decision. This is the rule that keeps everything healthy:AI is most valuable when it helps you explore, not when it tries to decide.It speeds up thinking, but it doesn’t replace judgment. Your team still owns the product decisions.From idea to interaction with Figma MakeIf AI helps you explore before Figma, Figma Make is where it becomes a serious workflow upgrade.Make is built for fast prototyping through conversation. Instead of building everything manually, you describe what you want, or paste an existing design, and Make generates a working interactive prototype.This is especially useful for mobile teams because the hardest part of mobile UX is often not the visuals, it’s the behavior:navigation patternsstate changesinputs and validationtransitions and flow continuityMake accelerates all of that.Conversational prototypingMake works like a collaborative assistant. You can ask for: core screens for a feature, alternate layouts for a flow, a basic navigation structure, and Interaction behaviors (cards, modals, tabs, etc.).For example:“Create a mobile home screen for a travel planning app with a search bar, destination carousel, and bottom navigation.”“Generate three alternative layouts for a booking flow with date selection and traveler details.”“Build an interactive prototype for exploring points of interest, including card interactions and a map view.”Instead of staring at a blank canvas, you start with something functional.Structure plus logic (not just mockups)The major difference between Make and traditional quick mockups is that it generates more than layout.Make supports interactive behavior, allowing you to preview: transitions, form inputs, navigation patterns, and data-driven states.If you want realism, it can even connect to external data sources like Supabase to simulate an app that responds dynamically rather than remaining purely visual. That matters because mobile teams don’t ship static screens. They ship systems.Early validation for designers and developersThis is where Make becomes a shared tool. Designers get faster iteration and can explore alternatives without rebuilding everything manually.Developers benefit because:the interaction logic becomes clearer earlystate behavior is easier to evaluateedge cases surface soonerthe “what happens when…” questions get answered before implementationInstead of debating a flow in abstract terms, the team can test it in a working prototype.The right way to use Make: iterative, not giant prompts.Make has a token budget per request. If you try to generate an entire app in one prompt, it will break or degrade. The best workflow is:Generate one view or interaction.Refine it.Add the next piece.Build the flow step-by-step.This gives you higher reliability and more creative control, and avoids treating AI as a “magic button.”A bridge to production, not a detourOnce the prototype matches your intention, you can move it into Figma Design and refine: visual language, design system consistency, spacing and layout precision, and final interaction polish.Make also produces inspectable code under the hood, which can help developers understand what’s being proposed and reduce ambiguity.Designing with handoff in mindAI doesn’t stop being useful once you enter “real design.” In fact, this is where it becomes most practical. Mobile teams lose time in handoff because of translation gaps:designers describe behavior in one waydevelopers interpret it differentlyedge cases are missedimplementation diverges from intentAI can reduce this, not by replacing communication, but by making outputs clearer.Inspectable outputsWhen prototypes behave more like real products, handoff becomes less interpretive.Instead of handing off static screens and hoping the interactions are understood, teams can point to a working prototype that shows:what changeswhen it changeswhat the user sees in different statesThat’s especially valuable for mobile, where interaction patterns and state management are everything.Clearer documentationExternal AI tools can help you transform messy design notes into structured documentation. Claude is particularly strong at reading long content like:design system specscomponent behavior definitionsinteraction notesUX flow descriptionsIt can rewrite those notes into clean, consistent documentation that developers can actually use. ChatGPT is also strong here, especially when you need:multiple versions of an explanationsimpler language for stakeholdersa more technical tone for developersclearer state descriptions for componentsFewer translation errors between design and codeEven if AI never touches the final implementation, it still improves the handoff by improving the shared understanding.When developers understand component behavior faster, fewer details get lost, and fewer rounds of clarification are needed. AI doesn’t remove collaboration. It reduces friction in collaboration.Use AI as a multiplier, not a shortcutAI is at its best when it supports the work you already do, exploration, iteration, documentation, and alignment.It’s not a shortcut to good design. It’s a multiplier for good design thinking. If you treat it as a tool for speed with intention, it helps mobile teams:explore faster without pretending to know the answersprototype interactions earlier and more realisticallyalign on behavior before development beginsreduce handoff ambiguity and implementation driftDesign still requires judgment. AI just removes the parts that slow you down for no good reason.The most valuable impact of AI in design isn’t that it produces screens faster. It’s that it helps teams reach shared understanding sooner.When you use AI to explore ideas before Figma, prototype interactions quickly with Figma Make, and support documentation and handoff with clearer language, you reduce the gaps that slow mobile work down. Designers stay focused on judgment and quality. Developers get cleaner intent, fewer surprises, and more predictable implementation.AI is not a shortcut around good design. It’s a multiplier for teams that already care about doing it well, and a practical way to keep speed, clarity, and craft in balance.To learn more about Figma, check out the third edition of Designing and Prototyping Interfaces with Figma by Fabio Staiano.📘 Third edition of the bestselling book, updated with a new project, refreshed interface, and the latest design trends🧩 Build adaptive, production-ready UIs with variables, modes, components, variants, AI, and Auto Layout🔀 Prototype branched flows with conditional interactions and interactive componentsDesigning and Prototyping Interfaces with FigmaBuy now at $39.99This week’s news cornerNow that we’ve covered how AI can reduce friction inside Figma, let’s look at this week's news, where that same idea shows up often.Xcode 26.3 brings AI coding agents directly into iOS development: Apple’s Xcode 26.3 introduces agentic coding support, allowing iOS and macOS developers to use AI coding agents like Claude Agent and OpenAI Codex directly inside Xcode. These agents can explore documentation, adjust project settings, and assist across the build cycle. With Model Context Protocol support, developers also get more flexibility to plug in compatible AI tools into their app development pipeline.Kotlin 2.3.0 released: Kotlin 2.3.0 is out. It introduces unified companion object access across all JavaScript module systems. This will let exported companion objects behave the same way in ES modules, CommonJS, AMD, UMD, and more, which eliminates the previous inconsistencies in how they were accessed from JS/TS code. It also simplifies Kotlin/JS interop and avoids bugs caused by differing access patterns depending on the module system.iOS 26.4 beta could unlock major Siri upgrades for developers: Apple is expected to release the first iOS 26.4 developer beta during the week of February 23. This update could be a key milestone, as Siri is expected to gain deeper app integration features like on-screen awareness, personal context, and the ability to take actions inside apps. If delivered as promised, iOS 26.4 may open new opportunities for building more intelligent, voice-driven iOS experiences.Accelerating your insights with faster, smarter monetization data and recommendations: Google is rolling out enhanced monetization insights and actionable recommendations in the Google Play Console. It will provide developers with a clearer visibility into key business metrics like conversion, churn, ARPPU, and revenue drivers. With these updates, developers can make data-driven decisions faster, prioritize improvements with estimated ROI, and integrate real-time order data via the Orders API that will let you to track performance better and optimize app business outcomes.New Apple-backed AI model can generate sound and speech from silent videos: Apple and partners have developed a unified AI model called VSSFlow. This model can generate both sound effects and speech from silent videos using a single system. This addresses the limitations that existed in separate video-to-audio and speech generation models. Developers can utilize this new tech to enable richer multimedia features, faster prototyping of audio-visual interactions, and new accessibility possibilities by automating synchronized sound and speech creation directly from video content.👋 And that’s a wrap! We hope you enjoyed this edition ofMobilePro. If you have any suggestions and feedback, or would just like to say hi to us, please write to us. Just respond to this email!Cheers,Runcil Rebello,Editor-in-Chief, MobilePro*{box-sizing:border-box}body{margin:0;padding:0}a[x-apple-data-detectors]{color:inherit!important;text-decoration:inherit!important}#MessageViewBody a{color:inherit;text-decoration:none}p{line-height:inherit}.desktop_hide,.desktop_hide table{mso-hide:all;display:none;max-height:0;overflow:hidden}.image_block img+div{display:none}sub,sup{font-size:75%;line-height:0}#converted-body .list_block ol,#converted-body .list_block ul,.body [class~=x_list_block] ol,.body [class~=x_list_block] ul,u+.body .list_block ol,u+.body .list_block ul{padding-left:20px} @media (max-width: 100%;display:block}.mobile_hide{min-height:0;max-height:0;max-width: 100%;overflow:hidden;font-size:0}.desktop_hide,.desktop_hide table{display:table!important;max-height:none!important}}

Make sure to subscribe our BIPro Newsletter so you never miss a key update in the data world. Join over 35K+ BI lovers and get tips from those who’ve cracked tough data challenges!IntroductionA well-designed semantic model is the foundation of every effective Power BI report. It defines how data tables connect, how calculations behave, and how insights are ultimately presented to users. Without a solid semantic model, even the most visually appealing reports can produce misleading or inconsistent results. In this article, you’ll learn how to create and explore a semantic model in Power BI, understand the Model view, and build relationships that allow data to aggregate correctly across tables, setting the stage for accurate analysis and meaningful business insights. Technical requirementsThe following are needed in order to successfully complete the instructions provided in this chapter:An internet connectionMicrosoft Power BI DesktopChapter 5 Start.pbix downloaded from GitHub at https://github.com/PacktPublishing/Learn-Microsoft-Power-BI_3ECreating a semantic modelThe concept of a semantic model, data model, or dataset is fundamental to Power BI. In short, a semantic model is defined by the tables that are created from Power Query queries, the metadata (data about data) regarding the columns within the tables, and finally, the relationships that are defined between tables. Relationships are needed to connect individual tables to one another. In Power BI, the semantic model is stored within an Analysis Services tabular cube. It is the creation of this semantic model that enables self-service analytics and reporting.In Chapter 4, Connecting to and Transforming Data, we connected to various sources of data (three different Excel files) that in turn created seven different queries, which ultimately resulted in four queries that loaded data tables into our semantic model. We can now stitch those individual tables, along with our previously created data table, into a cohesive semantic model that is used for further analysis.If you are continuing from Chapter 4, continue to use the same Power BI Desktop file after completing that chapter. Otherwise, download and load Chapter 5 Start.pbix as specified in the Technical requirements section of this chapter.Touring the Model viewSo far, we have explored the overall architecture of Power BI Desktop and Power Query Editor. We will now explore the Model view within Power BI Desktop. To switch to the Model view, click the third icon from the top in the Views bar of Power BI Desktop.The Model view is shown in the following screenshot:Figure 5.1 – Model viewThe Model view provides an interface for building our semantic model. It does this by creating relationships between tables, as well as defining metadata for tables and columns. We can even create multiple layouts for our semantic model. The Model view interface is similar to other Desktop views, as shown in Figure 5.1:Header: As shown in Figure 5.1, the Header area is identical to what was described in the Touring the Desktop section of Chapter 3, Up and Running with Power BI Desktop.Ribbon: The Ribbon is nearly identical to what we described in the Touring the Desktop section of Chapter 3, Up and Running with Power BI Desktop, with the notable exception that only three tabs are available—that is, File, Home, and Help. If third-party extensions are installed, the External tools tab is also present.Views: The Views area is identical to what was described in the Touring the desktop section of Chapter 3, Up and Running with Power BI Desktop.Canvas: As mentioned in the Touring the desktop section of Chapter 3, Up and Running with Power BI Desktop, when in the Model view, this area displays layouts of tables within the semantic model, as well as their relationships to one another. A default All tables layout is created automatically.Panes: As described in the Touring the desktop section of Chapter 3, Up and Running with Power BI Desktop, only two panes are present—the omnipresent Data pane and the Properties pane. The Properties pane is exclusive to the Model view and allows us to associate metadata with various fields or columns within the tables of the semantic model. This includes the ability to specify synonyms and descriptions, as well as data types, data categories, and default aggregations or summarizations.Layouts: The Pages area from the Report view is replaced by Layouts. The Layouts area allows us to create multiple layouts or views of the data tables within the model, as well as to rename and reorder the layouts.Footer: As described in the Touring the desktop section of Chapter 3, Up and Running with Power BI Desktop, in the Model view, the Footer area provides various viewing controls, such as the ability to zoom in and out, reset the layout, and fit the model to the current display area.This completes our tour of the Model view. Let’s next see how we can change the layout of our semantic model.Modifying the layoutIn the Model view, we have a default All tables layout, which was created for us automatically by Power BI.To modify this layout, follow these steps:1. Minimize the Data and Properties panes by clicking on the arrow icon in the pane headers (>).2. Click on the tables and drag them closer together. Use the Fit to screen icon at the far right of the Footer to zoom in on the table layout. You should now be able to clearly see the table names and columns in the tables.3. Move the Calendar and People tables next to one another in the top center of the Canvas by clicking on and then dragging and dropping. Place the Budgets and Forecasts and Hours tables underneath these two tables. Use the Fit to screen icon in the footer to zoom in on the tables. Note that we cannot see all of the columns in the Hours table or the Calendar table. A right-hand scroll bar is present on both tables.4. Use the sizing handle in the bottom-right corner of the table to adjust the size so that we can see all of the columns in the table. When finished, your Canvas should look similar to this: Figure 5.2 – Data tables in the modelNow that we have modified the layout such that we can easily see all tables on the screen, let’s continue building our semantic model by defining relationships between the individual tables.Creating and understanding relationshipsNow that we can clearly see our tables and columns, we can create relationships between our tables. Creating relationships between tables allows calculations and aggregations to work across tables so that multiple columns can be used from separate, related tables.For example, once the People table and the Hours table are related to one another, we can use the ID column from the People table and the TotalHoursBilled column from the Hours table. By doing this, TotalHoursBilled aggregates correctly for each user Identifier (ID) in the People table.To create this relationship between the People table and the Hours table, click on the ID column in the People table and drag and drop it onto the EmployeeID column in the Hours table. The New Relationship dialog is displayed, as follows:Figure  – New relationship dialogClick the Save button and note that a line appears on the canvas that connects the People table to the Hours table. This creates a relationship between the ID column in the People table and the EmployeeID column in the Hours table.You can check the columns that are involved in a relationship by hovering your mouse over the relationship line. The line changes slightly and the columns involved in the relationship become shaded.Figure  – Relationship between two tablesIf you notice that ID and EmployeeID are not columns associated with the relationship, hover over the relationship line, right-click it, and choose Delete. Then, try again.Note that the line has 1 next to the People table and * next to the Hours table. This means that this relationship is one-to-many or many-to-one.In other words, there are unique row values in the People table that match multiple rows in the Hours table. This makes sense since each employee submits an Hours report for every day. The designation of 1 (unique) or * (many) defines the cardinality of the relationship between the tables.There are actually four different cardinalities for relationships in Power BI, as outlined here:One-to-one: This means that there are unique values in each table.Many-to-one: This means that there are unique values in one table that match multiple rows in another table.One-to-many: This means that there are unique values in one table that match multiple rows in another table.Many-to-many: This means that neither table has unique values for rows. It is generally good practice to avoid these types of relationships because of their complexity and the amount of processing and resources required.The designation of many-to-one versus one-to-many is simply a matter of which table is defined first within a relationship. In other words, the relationship between our People table and Hours table could be either many-to-one or one-to-many, depending on which table we defined first in our relationship.Note that there is also an arrow icon in the middle of the line that points from People to Hours. This indicates that the People table filters the Hours table, but not vice versa. This is known as the cross-filter direction. Cross-filter directions can be either Single or Both, meaning that the filtering occurs only one way or bidirectionally. In simple semantic models, you generally don’t have to worry about cross-filter direction, but it can become very important if the complexity of the semantic model increases.Finally, note that the line that forms the relationship between the tables is solid. A solid line indicates an active relationship. Inactive relationships can be created between tables, and these are represented as a dashed line. In Power BI, there can only be a single active path between tables.As models become more complex, multiple paths from one table to another can be created. In those cases, one or more of the relationships or pathways become inactive. However, even though the relationship is inactive by default, it can be used within calculations that specify using specific relationships.We can view and modify the relationship definition by double-clicking on the relationship line. This brings up the Edit relationship dialog, which looks nearly identical to the New relationship dialog shown in Figure 5.3.Note that since the Hours table is defined first and the People table is defined second, the Cardinality value of our relationship is Many to one (*:1). Also, note that the relationship is active and that the Cross filter direction value is Single.In many-to-one and one-to-many relationships, a Cross filter direction value of Single means that the one side of the relationship filters the many side. Finally, note that the EmployeeID column in the Hours table and the ID column in the People table are highlighted in gray. This shows us the columns that form a relationship between the two tables. Close the Edit relationship dialog by clicking the Cancel button.Now, let’s create another relationship, this time between our Calendar table and the Hours table. To do this, we can use the Manage relationships functionality, as follows:1. Click on the Home tab of the ribbon. Then, in the Relationships section, choose the Manage relationships button. The Manage relationships dialog is displayed, as shown in the following screenshot:Figure 5.5 – Manage relationships dialogHere, we can see our existing Active relationship between the Hours table and the People table, including the columns involved in the relationship in parentheses. From this dialog, we can Edit or Delete the relationship or have Power BI attempt to Autodetect relationships between tables. Power BI can sometimes autodetect relationships between tables based on the column names and row values.2. Select the + New relationship button. This displays the New relationship dialog, as shown in the following screenshot:Figure 5.6 – Create relationship dialog3. In the first drop-down menu, choose the Hours table. A preview of the table will be displayed.4. Click the Date column.5. Choose Calendar in the second drop-down menu. A preview of this table is displayed.6. Choose the Date column from this table. Power BI detects the appropriate Cardinality and Cross filter direction values. Since there are no other relationships between these tables, Power BI checks the Make this relationship active checkbox.7. Click the Save button to create this relationship. Note that this new relationship now appears in the Manage relationships dialog.8. Click the Close button to close the Manage relationships dialog. In the canvas, there will now be a relationship line linking the Calendar table to the Hours table.Congratulations—you have successfully linked the three separate tables to create a semantic model!For now, we won’t link the Budgets and Forecasts table within our semantic model. This is a good time to save your work.Now that our semantic model is created, let’s explore our semantic model a little closer by creating some visuals.Exploring the semantic modelBefore we move on, let’s do some exploration of our data in order to understand our data, our semantic model, and how this data can ultimately be viewed by end users. To do this, follow these steps:1. Start by clicking on the Report view in the Views bar.2. At the bottom of the report canvas, click the plus (+) icon next to Page 1. This creates a new blank page, Page 2. Double-click Page 2 and rename it Utilization, and then press the Enter key. This changes the name of the page to Utilization.3. Expand the People table in the Data pane by clicking the small arrow to the left of the People table. Check the box next to the Name field. This creates a Table visualization on our report canvas with the names of employees. Use the sizing handles for this visualization to resize the table to take up the entire page.4. Expand the Hours table. Make sure that the table visual is selected and then check the box next to the Hours field. The number of hours reported by each employee is shown next to their name. This occurs because of the relationship between our People table and our Hours table. Because these tables are joined by a relationship based on the ID of each employee, we can use fields from both tables in visualizations. Due to this, the rows in the Hours tables are automatically filtered based on this relationship.Note that when the Table visualization is selected, the Hours and People tables have small checkmarks next to them. This indicates that the visualization contains fields from these tables.5. We know that the Category field of the hours is important, regardless of whether the hours are billable or not. With the table selected, click on the Matrix visualization in the Visualizations pane. This icon is to the immediate right of the highlighted Table visualization. Note that the Build visual pane changes from just displaying a Values field well to now containing field wells for Rows, Columns, and Values. Our Name field is now under Rows, while our Hours field is under Values and shows up as Sum of Hours.6. From the Hours table, click on Category and drag and drop this field into the Columns field well. We can now see a breakdown of the hours for each employee by category.It is now obvious that we can calculate a simple version of our utilization metric by taking the number of Billable hours for each employee and dividing them by the Total number of hours for each employee. Save your work before continuing.ConclusionBuilding a semantic model in Power BI is a critical step in transforming raw data into reliable, self-service analytics. By organizing tables, defining relationships, and understanding how filtering and cardinality work, you enable calculations and visuals to behave as expected across your reports. This foundation not only improves accuracy and performance but also makes your Power BI solutions easier to scale and maintain over time.If you’d like to explore this topic in greater depth with guided examples, best practices, and real-world scenarios, you can learn more in Learn Microsoft Power BI - Third Edition by Greg Deckler, where semantic modeling and calculations are covered as part of a complete, end-to-end Power BI learning journey. This book helps you master self-service BI and become your team’s data hero or launch a new career. You’ll learn how to clean data, build models, and use advanced analytics in Power BI to unlock valuable insights and drive better business decisions.Author BioGreg Deckler is a Vice President at a global consulting services firm. In addition, I am a 7-time Microsoft MVP for Data Platform. As an active member in the Columbus IT community, I founded the Columbus Azure ML and Power BI User Group (CAMLPUG) and have presented at many different conferences and events including Dog Food, SharePoint Saturday, CloudDevelop and M3. I am also the author of Microsoft Hates Greg's Quick Measures (MSHGQM) tool and the associated YouTube channels Microsoft Hates Greg and DAX For Humans.