Bhoomika Shiyani

So hi. My name is. I am from India, and I have a total work experience of 4.5 years now. And I basically have done my graduation from business management. Then I eventually found out my interest in designing. So that is why I have chosen a 1-year diploma course for computer applications, which is post-lecture diploma in computer applications. So in that, I have learned a lot of things about development and design. And in the development part, I learned PHP, Java, HTML, CSS, and a lot of languages. And then I figured out that my initial interest is not in development. It is in design. So then I found an internship in design only. So where I worked for 6 months, and it was basically a web development internship, but then I got some more time from the internship and then started working on design. And after completing that internship, I got a job in UI UX Design. So that was my first job. And then I started to dig deeper in the field and in this industry. After that job, I worked with a design agency, where my design experience got enhanced because it was a pure design work agency. No developers were there. Only designers were working together on various projects over the span of 2 plus years. I worked on more than 10 to 12 different projects, which include fitness, health, edtech, CRM, and various projects. And after that, I have worked in the Fintech domain as well. So currently, I'm in the Fintech domain, and I'm looking forward to explore more domains and diversify my skill set, and to solve more complex business problems.

Yeah. So while designing in Figma, I always try to create if we are designing a web page or a landing page of a product. Right? So I always keep the first option in 1920 by 1080 format only for the bigger screens. Okay? That is the biggest size we have, which is 1920 pixels by 1080 as a height of the landing page. Right? So first, I design for that only. When after that, when the requirement comes to go for responsiveness and the design elements would be adjusting as per the screen size changes. So for that, I prefer to go for the 1440 by 1080 size. So I'm designing that as well. And after that, the smallest one is 1260 by 768. So for the web pages, we have to create three variations with three different sizes, and then we have to define grids as well so that each and every design element would be consistent in every screen size. Right? And the same goes for the mobile application as well. So for the Android phones, it is around 360 by 800. Right? And so first of all, I design each and every mobile app in the size only if it is for Android. And if it is for iOS, then we have to consider 375 as a width and 800 as a height for iOS. And then we have to also keep in mind the human interface guidelines for iOS and material design guidelines for Android. So we can give a spacing according to their design system. So to make the app visually better in the real world. So whenever the user downloads the application from the Play Store or App Store, it should be pixel perfect, and it should not cut the design elements from the edges of the phone or anything. So I keep various device commands in my design system, and I always try to make the elements responsive.

Yeah. So Figma's collaboration feature is very good because whenever I am working and you are my client. Right? So if you want to see what I'm working on and how I'm working, I will share the Figma link with you, and you can easily track me or follow me on that so that you can see in real-time where I'm working, what I'm working on, and the progress. Right? So, Figma allows the client to continuously observe the candidate on the file, right? Then you can also comment wherever we are reviewing the designs and everything. You can put comments on whatever part you want to input. So that's also another way to streamline the design process with stakeholders. Right? And you can also tag me so that I will get an email notification that the following person has commented here on this file. Right? So this is how we can collaborate in Figma to make the design process streamlined and get more productive work done.

Yeah. So Figma has a lot of things in hand. So they have this Figma software, which is for wireframing and UI design. And for the end, they also have FigJam where we can sit together and brainstorm on product ideas to better understand complex business requirements. We can definitely divide complex business requirements into smaller parts, like in small parts. And then we can pick one small part and work toward solving it. So that's how we can divide the requirements into smaller parts. And then after taking each smaller part, we can solve the business problems. We can use FigJam to create user personas, user journey maps, create empathy maps, collect all user research, and create mood boards to define the UI design style and the direction we should move forward. We can decide that from the mood board. So we can do a lot of things in FigJam. And after doing all of this in FigJam, we can directly import that into Figma to better understand complex business requirements and streamline the UI design. We can sync with the research and validate it with the features we've done. So Figma's features are really cool, and they're also integrating AI. So we can create more intuitive and attractive and elegant UI designs in Figma with the help of AI.

Yeah. So I always keep in mind about the developers, whether they would be able to develop this kind of feature. Because we have a lot of technicalities in the development of the application and everything. So we have to be sure if we are designing for Android, then we have to keep all of the technical constraints in mind regarding material design and the Android operating system. Right? And in the meantime, if we are designing for Android, we can read the guidelines for material design. So, basically, we definitely need to keep in mind the spacing of the elements and how Android responds to that spacing and how it will look on a mobile device if someone is using it. So we have to test it with real mobile devices, and then we have to adjust our designs and everything. So it would be really great if we can test all of these visual things in the wireframe stage only so that we can create a seamless user experience, and we can balance the technical constraints. And also, the developers will not have to worry about any of the forms or solutions for our complex business requirements.

Yeah. So, basically, Figma provides a lot of features. We can definitely create various components for our design system for our new product in Figma. And after creating all of those components, a design system is a collection of components, such as colors, typography, spacing, and components like accordion checkboxes, radio buttons, and things like icons, progress bars, loaders, and many other components. It varies product to product. Right? So, after creating all of this, we can check the accessibility standards with the help of Figma plugins. Plugins are add-ons. Okay. With the help of add-ons, we can check the accessibility standards, such as WCAG and other accessibility standards. It's our component. We have created a component. Whether it passes the accessibility standards or not, if it doesn't, we can adjust our design system colors in advance before going much further. Right? So, that we can create a seamless user experience with the help of Figma plugins, which allow you to check accessibility standards and contrast between colors and each component of the application, so that we can create a seamless user experience to enhance the user's emotions and their experience.

I have not worked with this Leap code. I'm a pure designer. So I don't think that I would be the suitable person to answer this question because I have only worked in design, and I am not a developer. So I don't think I would be a suitable person to answer this question.

I am a pure designer. I only make designs in Figma, and I'm not a developer. I actually didn't want the opportunity to explore JavaScript and create all other things. So, I'm not the suitable person to answer this question.

Yeah. Definitely. The auto layout feature is the biggest problem solver in the Figma software. Right? Because earlier, what happened is that if we're you know, for example, you have a requirement that involves creating various screens for various devices. So for if we have designed a home screen, then I need to create that home screen variation for larger devices, medium devices, and smaller devices. For example, let's take a look. Let's take an example of a landing page. So firstly, I have created that landing page for the website for the laptop screen. Then I have to create that in a tablet screen, and then I have to check how the website would look in a mobile screen. So these are three various devices that I need to consider. Okay? So what it used to be earlier before auto layout came, it was like you have to create a set of components three times. Right? Because you first have to create the component for the web, then you have to create the component for the tablet, then you have to create the component for the mobile application. Right? So, you have to create one single component for three devices. So it will take a lot of time and effort and energy. But with the help of auto layout, we can create only one component, set the constraint, and set the other things. We can keep some things hidden as well, and we can set the constraint. Like, if the width of the screen is 1920, then display all of the elements. If the screen size is around a 1000 for the tablet, then hide these many things and display only these things. And if the screen size is for mobile, then we can also define that hide most of the things and display fewer things in the mobile screen. So with the help of only one component, we can create various things for various devices. So this is the power of auto layout, and I strongly believe in using auto layout in all of my designs. Right? And it is the main game changer in the design industry.

I couldn't get an opportunity to explore the login thing, login creation that is in my bucket list. I would definitely plan something for the plugin creation, and it is in my to-do list because I want to try this plugin creation functionality because I can, with the help of that, learn about some coding languages and some other things. And, definitely, I can create one plugin that can really change a real-world problem in Figma. So, definitely, it is in my bucket list, and I will once I get the opportunity, work on creating plugin creation and custom screens.

I actually haven't had any opportunity to work with Sigma's API to automate repetitive design tasks. And if I were given the chance to work with that, I would definitely put a repetitive task on automatic mode so that I could focus more on solving another challenge and some predefined tasks would be going on autopilot mode. So, definitely, I could focus more on solving more complex business challenges, and I shouldn't waste my energy on creating this repetitive design task. That's how I'm planning to work if I were given the chance to work with that, I would definitely try that, and I would do all of my tasks.