Astronaut loading animation Circular loading bar

Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(7)

Customer Journey(16)

Design(39)

Solar Industry(7)

User Experience(62)

Edtech(10)

Events(34)

HR Tech(3)

Interviews(10)

Life@mantra(11)

Logistics(5)

Strategy(17)

Testing(9)

Android(48)

Backend(32)

Dev Ops(8)

Enterprise Solution(28)

Technology Modernization(4)

Frontend(29)

iOS(43)

Javascript(15)

AI in Insurance(36)

Insurtech(63)

Product Innovation(54)

Solutions(21)

E-health(11)

HealthTech(23)

mHealth(5)

Telehealth Care(4)

Telemedicine(5)

Artificial Intelligence(139)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(17)

FinTech(51)

Banking(7)

Intelligent Automation(27)

Machine Learning(47)

Natural Language Processing(14)

expand Menu Filters

Understanding the Why’s in designing

We have been ingrained with a lot of rules and regulations since our childhood. And out of curiosity, whenever we asked why, the answer was- some traditions and customs must be followed…😤

And this didn’t end there, even in UI/UX too, the same is followed even today.

So many rules and no clear explanation of  Why.❓

In this blog, we’ll try to understand the reasons why certain guidelines must be followed when designing. For example, why we shouldn’t use red background on blue and vice-versa? Why button should have a certain touch area? And so on.
To begin with, the majority of the rules related to the design are actually connected with how the human body is structured or as we call it, Designed. Not clear? We’ll go one by one discussing the reasons behind most widely used 6 rules. 

1. Why is Red font on a blue background is big NO ❌?


The choice of font color and the background color is usually based on factors such as contrast, legibility, and aesthetic appeal. However, it is important to ensure that the combination of colors provides good contrast, making the text easy to read. But why is it hard to read?

This occurs because of Chromostereopsis, which is a visual illusion that happens when certain colors are placed next to each other, making it unnecessarily difficult to stay focused on both colors. The illusion is due to the stimulating of different areas within the eye, causing some light rays to coincide with others in the eye. Because of this, it becomes difficult for the human eye to focus on them.

2. Why Recognition is better than recall?

Don’t let users remember!
As a designer, we should always try to reduce the user’s memory load by keeping objects, actions, and options visible. The user shouldn’t have to recall details from one section of the dialogue to the next.
Why?
Because of short-term memory. 

The majority of the information in short-term memory will be stored only for about 20 to 30 seconds, or even less, and can last for up to just a minute.


Most information decays quickly, unless we rehearse it. We remember 7 things, +/- 2 in short-term memory. Recent research shows a decrease to 4 things +/- 1.
That’s how our brain is designed. So it becomes hard for the users to remember information, it’s always best to recognize the information than recalling.

Oops! I forgot which account number I selected 🤯😶‍🌫️


3. Why Larger Button size (touch area) must be used? 

​​The button size should not be less than 42 pixels(not a hard and fast rule). This is not because of visual appeal, balance, etc., but because of the thumb/ finger touch area. The smaller the size, difficult it becomes for the user to perform actions using the button or icons in that case. And larger items are easy to see.


4. Why too many Fixations isn’t good for the user? 

The brain assembles a continuous visual experience from a sequence of fixations and saccades, making vision continuous. Fixation is the location at which our eyes fixate and a saccade is a fast, simultaneous movement of both eyes between two or more phases of fixation in the same direction.
Things that attract the scan are bright colors, big numbers, people, etc.
Too many fixations make it difficult to scan through the design, it recreates too much cognitive load. So we have to reduce eye fluctuation to keep the focus and to get the work done easily and efficiently.


5. Why is the Floating icon always on the right end?


Ever wonder why floating icons are on the right end of the phone? This is because of the way people naturally read and scan content. The floating icon concept is connected with how our motors (hands) and eyes function. In many cultures, people read and scan content from left to right. This means that their eyes are more likely to start on the left side of the screen and move toward the right. And also most Indians are right-handed and the right end is the easiest area to be accessed while using the phone. Anywhere on the top becomes difficult to access.


6. Why success icon is green and the alert red?


The use of green and red colors to represent success and alert respectively is commonly used in user interface design. This is based on the psychological associations that people tend to have with these colors. Green is often associated with positive emotions such as growth, harmony, and success, while red is associated with danger, warning, and urgency.

And in the real world, the traffic signal-go is green, and the stop is red. Using the same color for success and alert becomes easy to associate with less or no cognitive load.

Wrapping Up:

These are just a few whys and they are many more. Learning the why behind these rules may help in making work more meaningful and becoming a good designer. 

Hope you found this article helpful. 

Want to know more about designing?

Read our blog: Iteration Leads to powerful results in Design

About the Author: 

Charishma is a UI/UX designer at Mantra Labs, who believes in creating experiences that matter. She is an MBA turned designer who fell in love with the process of how design is made.

Cancel

Knowledge thats worth delivered in your inbox

Platform Engineering: Accelerating Development and Deployment

The software development landscape is evolving rapidly, demanding unprecedented levels of speed, quality, and efficiency. To keep pace, organizations are turning to platform engineering. This innovative approach empowers development teams by providing a self-service platform that automates and streamlines infrastructure provisioning, deployment pipelines, and security. By bridging the gap between development and operations, platform engineering fosters standardization, and collaboration, accelerates time-to-market, and ensures the delivery of secure and high-quality software products. Let’s dive into how platform engineering can revolutionize your software delivery lifecycle.

The Rise of Platform Engineering

The rise of DevOps marked a significant shift in software development, bringing together development and operations teams for faster and more reliable deployments. As the complexity of applications and infrastructure grew, DevOps teams often found themselves overwhelmed with managing both code and infrastructure.

Platform engineering offers a solution by creating a dedicated team focused on building and maintaining a self-service platform for application development. By standardizing tools and processes, it reduces cognitive overload, improves efficiency, and accelerates time-to-market.  

Platform engineers are the architects of the developer experience. They curate a set of tools and best practices, such as Kubernetes, Jenkins, Terraform, and cloud platforms, to create a self-service environment. This empowers developers to innovate while ensuring adherence to security and compliance standards.

Role of DevOps and Cloud Engineers

Platform engineering reshapes the traditional development landscape. While platform teams focus on building and managing self-service infrastructure, application teams handle the development of software. To bridge this gap and optimize workflows, DevOps engineers become essential on both sides.

Platform and cloud engineering are distinct but complementary disciplines. Cloud engineers are the architects of cloud infrastructure, managing services, migrations, and cost optimization. On the other hand, platform engineers build upon this foundation, crafting internal developer platforms that abstract away cloud complexity.

Key Features of Platform Engineering:

Let’s dissect the core features that make platform engineering a game-changer for software development:

Abstraction and User-Friendly Platforms: 

An internal developer platform (IDP) is a one-stop shop for developers. This platform provides a user-friendly interface that abstracts away the complexities of the underlying infrastructure. Developers can focus on their core strength – building great applications – instead of wrestling with arcane tools. 

But it gets better. Platform engineering empowers teams through self-service capabilities.This not only reduces dependency on other teams but also accelerates workflows and boosts overall developer productivity.

Collaboration and Standardization

Close collaboration with application teams helps identify bottlenecks and smooth integration and fosters a trust-based environment where communication flows freely.

Standardization takes center stage here. Equipping teams with a consistent set of tools for automation, deployment, and secret management ensures consistency and security. 

Identifying the Current State

Before building a platform, it’s crucial to understand the existing technology landscape used by product teams. This involves performing a thorough audit of the tools currently in use, analyzing how teams leverage them, and identifying gaps where new solutions are needed. This ensures the platform we build addresses real-world needs effectively.

Security

Platform engineering prioritizes security by implementing mechanisms for managing secrets such as encrypted storage solutions. The platform adheres to industry best practices, including regular security audits, continuous vulnerability monitoring, and enforcing strict access controls. This relentless vigilance ensures all tools and processes are secure and compliant.

The Platform Engineer’s Toolkit For Building Better Software Delivery Pipelines

Platform engineering is all about streamlining and automating critical processes to empower your development teams. But how exactly does it achieve this? Let’s explore the essential tools that platform engineers rely on:

Building Automation Powerhouses:

Infrastructure as Code (IaC):

CI/CD Pipelines:

Tools like Jenkins and GitLab CI/CD are essential for automating testing and deployment processes, ensuring applications are built, tested, and delivered with speed and reliability.

Maintaining Observability:

Monitoring and Alerting:

Prometheus and Grafana is a powerful duo that provides comprehensive monitoring capabilities. Prometheus scrapes applications for valuable metrics, while Grafana transforms this data into easy-to-understand visualizations for troubleshooting and performance analysis.

All-in-one Monitoring Solutions:

Tools like New Relic and Datadog offer a broader feature set, including application performance monitoring (APM), log management, and real-time analytics. These platforms help teams to identify and resolve issues before they impact users proactively.

Site Reliability Tools To Ensure High Availability and Scalability:

Container Orchestration:

Kubernetes orchestrates and manages container deployments, guaranteeing high availability and seamless scaling for your applications.

Log Management and Analysis:

The ELK Stack (Elasticsearch, Logstash, Kibana) is the go-to tool for log aggregation and analysis. It provides valuable insights into system behavior and performance, allowing teams to maintain consistent and reliable operations.

Managing Infrastructure

Secret Management:

HashiCorp Vault protects secretes, centralizes, and manages sensitive data like passwords and API keys, ensuring security and compliance within your infrastructure.

Cloud Resource Management:

Tools like AWS CloudFormation and Azure Resource Manager streamline cloud deployments. They automate the creation and management of cloud resources, keeping your infrastructure scalable, secure, and easy to manage. These tools collectively ensure that platform engineering can handle automation scripts, monitor applications, maintain site reliability, and manage infrastructure smoothly.

The Future is AI-Powered:

The platform engineering landscape is constantly evolving, and AI is rapidly transforming how we build and manage software delivery pipelines. The tools like Terraform, Kubecost, Jenkins X, and New Relic AI facilitate AI capabilities like:

  • Enhance security
  • Predict infrastructure requirements
  • Optimize resource security 
  • Predictive maintenance
  • Optimize monitoring process and cost

Conclusion

Platform engineering is becoming the cornerstone of modern software development. Gartner estimates that by 2026, 80% of development companies will have internal platform services and teams to improve development efficiency. This surge underscores the critical role platform engineering plays in accelerating software delivery and gaining a competitive edge.

With a strong foundation in platform engineering, organizations can achieve greater agility, scalability, and efficiency in the ever-changing software landscape. Are you ready to embark on your platform engineering journey?

Building a robust platform requires careful planning, collaboration, and a deep understanding of your team’s needs. At Mantra Labs, we can help you accelerate your software delivery. Connect with us to know more. 

Cancel

Knowledge thats worth delivered in your inbox

Loading More Posts ...
Go Top
ml floating chatbot