Building A Power App: What's Next ?

By Ashwin Venugopal -

 





About

As you begin to explore the realm of app development and start working on your first application, there will be several common factors to keep in mind. Let's examine some of the more basic concepts.

Building For Different Devices

When starting to create Canvas apps from scratch, you have the option to select either a Tablet or Phone layout. Experienced Power Apps developers often suggest that this choice is not crucial since they incorporate responsive designs into their applications, making them adaptable to various devices. However, for those new to the process, selecting the tablet or phone format initially provides suitable screen dimensions to work with.

If your application will mostly be accessed by mobile users, opt for the phone option. If you intend to use your app in a web browser, within a Teams environment, or on a tablet, select the tablet option.

The Power Platform does offer the capability to automatically create apps, for instance, from SharePoint lists through the Integrate menu available in any list, but typically, you will have reduced control over the configuration. You will receive what the Power Platform determines is the most appropriate based on the data you are displaying.

Is The Look and Feel Important?

A Power App acts as a display for your data. If you design it attractively, users will come back frequently. However, if it’s disorganized, cluttered, and challenging to read, you won’t achieve the level of engagement and adoption you desire.

This topic is quite subjective and will vary among different creators and users of a Power App. Involving your users in the design process is advantageous, as they are the ones who will ultimately utilize it.

One important factor to consider is that when you finalize elements such as the color scheme, it becomes crucial to ensure they can be easily modified and adjusted. The colors and visual elements are defined within attributes referred to as Properties for the controls you integrate. Controls are the elements placed on the screen that either provide information or enable user interaction. For every control you incorporate, you will have numerous options or Properties available.

When it comes to colors for example, for a simple button control, you have properties such as:

Color - which determines the color of the button text

BorderColor - Which determines the color of the border

Fill - Which denotes the overall color of the button

HoverFill - Which denotes the color when a user hovers using a mouse

HoverColor - Which changes the text color when a mouse hovers over the button

Conclusion

Many basic concepts required to keep in mind while building an App are successfully discussed above.












Comments

Post a Comment

Popular posts from this blog

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more

How AMI Store & Restore Works?

By Ashwin Venugopal -
Image
  CreateStoreImageTask The CreateStoreImageTask API stores an AMI as a single object in an S3 bucket. The API initiates a task that collects all the data from the AMI and its associated snapshots, subsequently using an S3 multipart upload to store this data in an S3 object. It gathers all elements of the AMI, including most of the non-Region-specific metadata and all EBS snapshots included in the AMI, and consolidates them into a single object in S3. During the upload process, the data is compressed to minimize the space utilized in S3, which means that the S3 object could be smaller than the total sizes of the snapshots in the AMI. If the account making this API call has access to AMI and snapshot tags, they will be retained. The S3 object shares the same ID as the AMI, except it has a .bin extension. Additionally, the S3 metadata tags for the object include the AMI name, AMI description, AMI registration date, AMI owner account, and a timestamp indicating when the store operation...
Read more

Create A Store Image Task

By Ashwin Venugopal -
Image
  Introduction When you save an AMI in an S3 bucket, a task for storing the image is initiated. This store image task allows you to track the progress and result of the procedure. Securing your AMIs It is crucial to verify that the S3 bucket is set up with adequate security to protect the content of the AMI and that this security is upheld for the entire duration that the AMI objects are stored in the bucket. If this cannot be achieved, it is advisable to refrain from using these APIs. Make sure that public access to the S3 bucket is prohibited. It is suggested to activate Server-side encryption for the S3 buckets where you keep the AMIs, even though it’s not mandatory. When AMI snapshots are transferred to the S3 object, they are sent over TLS connections. It is possible to save AMIs that contain encrypted snapshots; however, the snapshots will be decrypted during the storing process. Identify the source AMI used to create a new Amazon EC2 AMI You can determine the AMI that was us...
Read more