Articles

How to Design an MVP Web Page

,

Learning how to design an MVP webpage or website could be one of the best things you can do as a site creator in today’s digital world.

In a fast-paced landscape, where customer preferences and technology are constantly changing, most companies don’t have time to dedicate months or years to each web project. The longer you take to complete your website, the more likely your creation will be outdated by the time you hit “publish.” That’s why countless creators are beginning to take a different approach.

To avoid wasting time, money, and effort on something that doesn’t deliver a significant return on investment, designers are now building “Minimum Viable Products,” or “MVPs.”

Here’s what you need to know about creating your MVP webpage.

What is MVP Web Design?

Typically, the “MVP” development process is most common in the app or software creation world. It refers to when a developer builds the simplest version of a technology capable of achieving specific goals. For instance, if a company wanted to create an ecommerce app, they would design a simple tool capable of listing products, enabling payments, and tracking orders.

After launching the MVP product, the company or developer would check to ensure it had the right impact on the target market and generated positive results. Using feedback and analytics, the developer would then begin to add new features one at a time.

MVP design aims to ensure you’re developing the best, most valuable product for your audience while getting your solution to market as quickly as possible.

The same strategy in MVP app and software design can also apply to website creation. Rather than building a highly complicated website with multiple features straightaway, the designer would focus on creating a single page equipped with the essential elements.

For instance, instead of building an entire site for your online course, you may develop a single-page website where customers can learn about the system, sign up, and pay for their membership. The great thing about an MVP web page is it allows companies to start advertising their solution, product, or service quickly, with the minimum initial investment.

How to Create an MVP Web Page

Creating an MVP web page is similar to designing any Minimum Viable Product. Throughout the project, the focus will be on keeping the development process simple while collecting as much feedback as possible.

Here’s how you’d get started with an MVP web page.

Step 1: Planning

Planning is an important stage in any web design project. It’s particularly crucial in the MVP landscape, where you need to define the most critical features of your webpage or website to ensure it’s “viable” for your needs. The initial planning stage can sometimes be the lengthiest part of the process, depending on the amount of research you need to do.

For the most part, web designers and companies will begin by conducting market research. This means examining crucial concepts intended to drive your strategy, such as:

  • Your target audience: Who are you trying to target with this web page, and what will they need from your site? A user persona can be helpful if you don’t already have one.
  • Competitors: Who are your main competitors in this space, and what do their web pages offer? Which features do you need to replicate or avoid?
  • Goal setting: What is the main objective of this web page? What do you need it to do, and what might it need to accomplish in the future?

The key to MVP web page planning is ensuring you look holistically at your project without thinking too far ahead. The site you create should be capable of scaling and expanding in the future, but it shouldn’t have too many features from day one.

Step 2: Creating Your Feature List

Once you’ve done your research and formed the foundations of your plan, it’s time to list all the features your MVP web page needs to have. Unfortunately, this is where the process can get a little complicated. It’s easy to start adding capabilities and components that aren’t necessary to make your site more exciting or competitive.

As worrying as it can feel to release a very basic web page, remember your focus is on rapid growth and development. With this in mind, concentrate on narrowing your feature lists down into:

  • Initial must-have capabilities: First, decide what your web page can’t thrive without. If the primary goal of your page is to sell software subscriptions, then you’ll need to implement tools for collecting member information and payments.
  • Next stage functionality: Consider the features you might add once you’ve confirmed your webpage is effective. This will allow you to ensure you’re creating a platform that can expand to suit future needs.
  • Possible future requirements: You can also list features that might be helpful in the future but don’t necessarily need to be implemented immediately. For instance, if you’re selling an online course, you might create a separate page where people can sign up to learn about future lessons.

Step 3: Finding the Right Software

Next, you’ll need to decide how to build your web page. There are several options available to today’s designers. An open-source solution is usually the best route for designers who need to create something specific from scratch. However, if the factor that makes your solution “viable” is unique, you may need access to code to bring your idea to life.

Alternatively, if you’re building a basic webpage capable of something like collecting customer email addresses or facilitating transactions, you might be able to use an off-the-shelf tool. CMS services for web designers can reduce the work and expense involved in creating a minimum viable product.

For instance, you might use a tool like Wix or Squarespace to edit a pre-existing template and simply drag-and-drop the features you need into the right places. On the other hand, if you’re planning on adding more functionality to your site down the line, it’s worth checking if any builder you will use has the right level of flexibility. Many tools will allow you access to code, advanced features, and essential module-based building functions.

Step 4: Implement Your Analytics

One of the essential parts of an MVP workflow is feedback. When you roll out your MVP, you’ll be looking for insights, guidance, and analytics to help you decide what your next steps are going to be. As a result, MVP workflows are based heavily on experimentation.

This means you’re going to need the right analytical tools in place to track crucial information. You can implement tools for collecting customer feedback directly. It’s also worth having a system in place for tracking metrics like:

  • Conversion rate;
  • Traffic numbers;
  • User behavior;
  • Most used/least used features;
  • Technical site performance;
  • Bounce rate;
  • Average time spent on the page.

While Google Analytics is one of the most popular tools for collecting insights in the MVP website design world, various other options are available. You can even find tools with in-built heatmaps to see how people navigate your site more effectively.

It’s also worth having A/B testing components in place. This will allow you to test the different “new” features you add to your web pages over time and examine how they influence your conversions and support your goals. For example, you can use A/B testing to explore the impact of everything from CTA button colors to webpage copy and offers.

Creating Your MVP Web Page

In the fast-paced web development and design world, the old-fashioned and slow approach to designing web pages is growing increasingly less common. Instead, an MVP strategy may be the best bet for companies looking to go to market faster, collect insights from their target audience, and accelerate growth.

Though getting used to this design strategy initially can be challenging, it can save you significant time, resources, and money in the long term.

 

HTML vector created by vectorjuice – www.freepik.com

Source

The post How to Design an MVP Web Page first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

14 Product Success Metrics to Measure Software Development Performance

,

There are several software products on the market that are used for their varied applications. This software makes the different tasks easier and allows for increased efficiency and performance. Development of any software is a tedious and long process, and it undergoes a series of quality and performance tests before its release and use. With the development in technology, the software gets upgraded with the latest updates.

As the technological world evolves, so do user expectations for handling applications; it is essential to test the performance of the applications before deploying them on a large scale.

Source de l’article sur DZONE

/par

Regression Testing in CI/CD and Its Challenges

,

The introduction of the continuous integration/continuous deployment (CI/CD) process has strengthened the software release mechanism, helping products go to market faster than ever before and allowing application development teams to deliver code changes more frequently and reliably. Regression testing ensures no new mistakes have been introduced to a software application by testing newly modified code as well as any parts of the software that could potentially be affected. The software testing market size is projected to reach $40 billion in 2020 with a 7% growth rate by 2027. Regression testing accounted for more than 8.5% of market share and is expected to rise at an annual pace of over 8% through 2027, as per reports from the Global Market Insights group.

The Importance of Regression Testing

Regression testing is a must for large-sized software development teams following an agile model. When many developers are making multiple commits frequently, regression testing is required to identify any unexpected outcome in overall functionality caused by each commit. The CI/CD setup identifies that and notifies the developers as soon as the failure occurs and makes sure the faulty commit doesn’t get shipped into the deployment. 

Source de l’article sur DZONE

/par

Release Management for Microservices: Multi vs. Monorepos

,

Imagine a microservice application consisting of dozens of continuously-deployed autonomous services. Each of the application’s constellation of services has its own repository, with a different versioning scheme and a different team continually shipping new versions.

Riddle me this: How can I tell the (whole) application’s version? Being that the change history is scattered among dozens of repositories, what’s the most efficient approach to keeping track of changes? And how do we manage application releases?

Source de l’article sur DZONE

/par

Continuous Delivery Patterns and Anti-Patterns

,

The goal for a successful continuous delivery process is to minimize the time it takes for development teams to go from idea to usable software by practicing agile techniques and automating the entire software delivery system: build, deploy, test, release. This Refcard explains detailed patterns and anti-patterns for core areas of CD, including the delivery and deployment phases, rollbacks, pipeline observability and monitoring, documentation, as well as communication across teams and within the organization.
Source de l’article sur DZONE

/par

Case Study: Redesigning Todoist for Android

,

Todoist is a to-do list app that 25 million people rely on every day to keep their lives organized. As part of the Doist design team’s goals for 2021, we aimed to redesign the Todoist Android app to take advantage of the latest Google Material Design guidelines.

In this post, we cover the design decisions and processes behind redesigning the Todoist Android app for Material Design. We explore the Design and Android team’s collaboration practices that brought the app update to life, which resulted in winning the Material Design Award 2021 in the large screen category. Let’s get started!

Opportunity

When we started the project, our design implementation on Android was ready for a major overhaul. The last milestone redesign on Android was initiated after the release of the first Material Design guidelines in 2016. Since then the team successfully worked on continuous improvements to the Android app, but we saw the opportunity to improve Todoist on Android on a more holistic level.

We set out to clean up instances of older UI components, colors, and text styles and update them with the latest Material Design components. We observed that some interactions and navigational patterns had become inconsistent with what users were expecting on newer Android devices and were eager to modernize this experience. With new hardware and software changes in mind, we set out to make the experience on larger phones and tablets even better, so Todoist could take full advantage of the latest generation of devices. Material 2 and 3 provided an incredible new framework to rethink the current app experience. With this in mind, we set out to challenge what a modern Android app should look like and innovate on top of the default user experience.

Solution

The team set itself the goal of redesigning our Todoist Android app and aspiring to make it the best-designed productivity app on Android. The project was ambitious and scheduled to take several months to complete. We set ourselves the following targets while working on the project:

  • Review the current implementation and older design specs.
  • Study the latest Material Design Guidelines and assess what is relevant for our project.
  • Research great Material Design apps and case studies and learn from their execution.
  • Define the new Todoist Android app design language and document the changes.
  • Design and development work together to assess the proposed solution and implementation.
  • Test an early version of the new app internally to gather feedback and make adjustments.
  • Invite beta testers to the new app to gather feedback and make adjustments.
  • Refine the app and address core issues before launching to the public.

Review

The project was kicked off by reviewing the current Todoist Android app implementation, noting down what areas needed to be fixed and what was up to date. While reviewing, we took screenshots of the app implementation for reference. This way we could easily see the current state of the app and compare it to the new design proposals that would be created. Once the review process was finalized, we had a comprehensive overview of the current state of the app and the layout, component, and styling changes we wanted to make.

Study

We continued the project by studying the latest Material Design Guidelines, assessing the components and practices that were most relevant to Todoist.

When the project kicked off in February 2021, Material 2 was the most recent version of their design system. Since Material 2 had already been released for quite some time, we anticipated that design changes to Material would be announced soon at the Google I/O event in May 2021. Rather than wait, because we expected the changes to be iterative, we pushed ahead with our work.

We identified 25 components and UI patterns that we wanted to change across the app. The changes included buttons, forms, menus, sheets, navigation drawer, app bar, system bars, text and color styles, and more. We started by creating a table view in a Dropbox Paper document with the component changes and references links to Google’s Material Design Guidelines.

This components list was a starting point for discussion to plan the scope and complexity of the changes. Close async discussions between the design and development team in Twist and Dropbox Paper comments helped us make decisions about scope and complexity early on and set a solid foundation for the project.

Research

In the initial Material Design study, we also researched inspiring Material Design apps, Material studies, Play Store apps, and Google Workspace apps to learn from their execution.

We started out by studying the Material Design Award Winners 2020 and tested out the products that were showcased. The showcased winners struck a good balance between implementing the Material Design Guidelines while maintaining their own product’s brand within the system. This balance between Google’s guidelines and the Todoist brand was also key for us to get right and so we strived to find this mix across the work we created and implemented in the project.

Along with the MDA winners, we researched the Material Studies that Google produced to showcase what apps could look like with branding and Material Design guidelines applied. It was a great reference to see how far components could be customized while maintaining the core platform principles. The Reply case study in particular offered valuable insight to us as its content type and layout came closest to Todoist. It showcased how components like the app bar, navigation drawer, and large screen layouts worked while being customized.

We continued our research by searching the Google Play store for inspiring app examples. Google Tasks, Press, Periodic Table, and Kayak stood out to us as the level of polish and quality of the apps were on par with the experience we were aspiring to create.

Sometime later in the project when Material You was released (more on that later), we stumbled upon the Google Workspace apps blog post which previewed Material 3 changes that Google was introducing to their own products. It offered a great glimpse at what was to come before the Material 3 Design Guidelines were officially released. This post sparked new internal discussions and further design explorations that we considered for future Todoist Android updates.

Design Spec

As we started to define the new Todoist Android app design language and document the changes, we opted to create a design framework, focusing on creating components rather than designing every screen in the app. This allowed us to consistently apply the design system in the app. We did so by using the previously defined component list that we created during the review and study process.

Core screens from different areas of the app were chosen to demonstrate how the components could be applied. We chose to mock up the Todoist project view, navigation drawer menu, project view edit screen, settings, and project detail view, among others. These screens gave us a good overview of how buttons, forms, drawers, lists, and other components would work together and in different states; selected, pressed, disabled, etc.

During the project, we were transitioning our Doist design system to Figma and started creating our first components in the new Doist Product Android Library. We started by using some components from the Material Design UI kit – Components library from the official Google Figma resource file and added them to our Doist design system. We then continued to build up the Product Android Library file with our Todoist-specific components such as task list & board views, detail views, sheets, colors, typography, etc.

We continued by documenting color and typography changes that were based on the Material Design guidelines. The design team opted to implement a new Design Token framework that would share the same values between our design system and the development implementation. The development team would output the values they had in the current implementation and the design team would analyze which values were needed and which could be merged, changed, or deleted. This informed the new Design Token color and typography system which we then documented and discussed with the team to implement. Later in the project, we were happy to see a similar token system introduced by Material 3 in the latest guidelines which validated our thinking and principles behind the new design system.

The design documentation expanded to hold other edge-case mockups that could sit alongside the design system. We documented different responsive screen experiences between phones and tablets against the previous implementation. Additional sections were created to document the motion that should be used for certain components and screens by referencing existing Material Design guidelines examples or prototyping custom motion in Principle and After Effects. The design spec also touched on haptic feedback that should appear on touch targets, how dark mode should work across the new components, documenting Todoist themes within the new design language, and more.

Design Implementation

At Doist, the benefit of the squad is that cross-team collaboration is built into the make-up of the team. Designers, developers, support, and product managers work together in a squad to deliver the project. This close collaboration from the start is key to bridging the gap between scope, estimations, design, development, and delivery. The squad discussed their findings on a daily basis and came up with the best plan of action together.

Designers started by creating components in Figma and shared them with developers in Dropbox Paper. We used screenshots to document the current implementation next to the new designs and linked to the default Google Material Design components. This allowed the team to compare all references in one place. Developers shared their feedback, adjustments would be brainstormed together as the designs were iterated.

Designers on the project would share their work in progress on a weekly basis with the rest of the design team in a design review Twist thread. Here details about the designs were discussed, alternatives mocked up and bigger picture plans made. Design reviews brought up topics like FAB (Floating Action Button) placement, theme options, accent color usage on components, consistency with other platforms, navigation options, and shadow elevation. After thorough discussions and alternative mockups were presented, the design team aimed to find the right balance between Material Design and Todoist brand guidelines. The development team, also part of the design reviews, gave their feedback on the solution and raised technical complexities early on.

Eventually, the design was stabilized and consistencies updated across components and mockups. The design spec was kept up to date so the development team could always review the latest designs in Figma.

Testing

As soon as the development process started, the Android team provided early screenshots and videos in Twist threads while they were implementing the design spec. This practice allowed us to review the app implementation early and often. Designers could review the development work and share feedback in Twist, which resulted in getting the implementation to a high quality. Alongside Twist discussions, the team set up a Todoist project to track ongoing issues and fix bugs. Designers logged new issues, developers would solve them and share the new implementation for designers to review.

When the team had the first stable version of the Android app, we shared it internally at Doist to get more insight and feedback. Other Doisters could access the redesign via a feature flag that could be turned on in the app settings and test the new version for however long they wanted. The feature flag system allowed people to give us early feedback on the design decisions we made and report bugs. Feedback was submitted by the wider team through a dedicated Twist thread and designers and developers could discuss how best to address the feedback during the active project implementation.

After we refined the app implementation further and addressed early feedback we opened up the app update to our beta users. Here users had access to the new Android redesign and were able to give us feedback. Our support team gathered feedback and shared it with us in a dedicated Twist thread. The squad aimed to analyze every comment and looked for patterns where we could make tweaks and improvements to the user experience.

As part of these tweaks, we made changes to how the bottom bar and navigation drawer worked. Some users reported frustrations with the way the new bottom navigation and menu drawer worked. In its first implementation, the drawer was half raised when opened and had to be swiped up to be raised again to see the full content list. This was an issue for some users as it was slower to get to the content below the list. So we decided to fully raise the drawer by default when opening. We also made it easier to open the navigation drawer by sliding up from the bottom app bar. This was a small shortcut but it enabled users to get to their content faster.

Material You

While we were in the testing phase and about to wrap up the project, Google unveiled Material You, and sometime later the Material 3 Guidelines were published. With the newly announced resources, we went back to study the latest guidelines and references we could find to see where the Todoist Android app redesign fits in and which adjustments we might need to make now or in the future.

Dynamic Color was a big new feature that was announced as part of the Material You update. As Todoist supports many different themes the Material You Dynamic Color feature seemed like a good fit for our product. We decided to prioritize this feature and implement Dynamic Color light and dark themes as part of our Todoist theme settings options.

To implement Dynamic Color, the development team started off by creating a demo prototype that utilized the Dynamic Color system and showcased how we could select from a range of color choices that the system defined based on the wallpaper choice. From there, we tried to incorporate system behavior in our design mockups. We designed a range of different color mockups and components to see which ones could fit with which components. We then came up with a color system that worked for the Todoist app and the new themes. These new Dynamic Color themes would sit alongside our current theme options in the Todoist app settings. From here users could choose between Dynamic Color Light and Dark themes.

Along with Dynamic Color, the team also created a customizable bottom app bar, allowing users to set up the app in a way that’s most convenient to their workflow. The location of the Dynamic Add Button can be changed to the center, left, or right corner of the screen. The order of the Menu, Search, and Notification buttons can be rearranged to best fit the ergonomics of the user’s dominant (left or right) hand and optimize their navigation patterns.

Launch

As critical beta feedback was addressed and stability tweaks were made, the squad felt ready to release the new Todoist Android app to the public. The team logged the issues that could not immediately be addressed for future reviews and updates.

The design and marketing team readied the launch by creating What’s New banner artwork and copy that are displayed within the app when launching the update. The Doist marketing team also created release notes and shared the app update announcements on our social channels. The brand and product design team worked together to create custom image assets and copy that summarised the project work in a simple and beautiful way.

What’s Next: Material 3

After a successful launch of the redesigned Todoist for Android app, Google contacted Doist to announce that Todoist was selected as the Material Design Award 2021 winner in the Large Screen category. The team was excited to be recognized for their hard work and it felt like we achieved the goal we had set out to accomplish.

Internally, designers and developers continued to study and discuss the Material 3 updates. The design team started exploring mockups and design changes inspired by Material 3 and Google’s Workspace app updates. Some of our current Todoist explorations include changing the FAB styling, updating the app bar, further removing elevation shadows, and more. Here is a preview of what a future Todoist update could look like.

We hope these insights into Doist’s design process and collaboration practices have sparked your interest. Thank you for reading and stay tuned for future design updates!

Takeaways

  • Study the Material guidelines, Material Design winners, Material studies, and Google Workspace apps to make informed design decisions when designing your next product or app update.
  • Evaluate which Material Design components and practices are right for you and implement them into your product.
  • Carefully balance the Material Design guidelines with your brand guidelines to create a unique and consistent experience between your product and the platform it lives on.
  • Collaborate with your Android developers early and often to ship app updates efficiently and increase the design implementation quality.
  • Use design components and build a design system along with practical mockups to create an efficient design spec.
  • Consider how the latest Android features fit into your product and which have the most impact on your users before deciding to implement them.
  • Test and review builds with your internal team and external beta users to get valuable feedback and make adjustments before releasing them to the public.
  • Create announcement artwork to showcase your latest app or feature update along with a clear description to share in-app and on social media.

Source

The post Case Study: Redesigning Todoist for Android first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Old Habits Die Hard, But Getting New Ones is Essential. Tips on Getting the Most Out of TypeScript

,

In web development, no one is surprised when a new framework or library enters the stage. Implementing complex functionalities and creating UI elements from scratch only using the powers of a specific programming language is not always the most optimal way. Instead, developers either rely on the existing frameworks or create their own for internal use. In the case of programming languages, the situation is a little more complicated.

A fairly large number of coders are unhappy with the limitations of the programming language that they use every day. Therefore, from time to time, we can hear about the new programming language release. The question is, will the development community adopt it as a replacement for well-established technologies? As an example, we can take a look at Dart. It was initially released in 2011 but remained quite unpopular until the Flutter framework was launched in 2017.

Source de l’article sur DZONE

/par

15 Best New Fonts, April 2022

,

This month’s collection of the best new fonts is headed in a lighter and quirkier direction than previous months. What’s more, font foundries seem to be getting more creative with their designs as many of these fonts come with alternative stylistic sets, giving you more control over the resulting typeface.

If you’re looking for some fun new fonts to spice up your web designs with, start here:

1. Beauty Rose

Beauty Rose is a whimsical script font that can add a touch of romance and warmth to header text and hero images. It would also look great when promoting holidays and events like Mother’s Day, Valentine’s Day, and weddings.

2. Black Sharp

Black Sharp is a bold display font that works equally well for website logos as it does for physical products (e.g., signage, packaging, book covers, etc.). What’s especially neat about this font is how it transforms when you change its texture. It takes on a very different tone with a grainy look instead of a shiny one, for instance.

3. Goat & Qalvigo

Goat & Qalvigo is a classic serif font with a modern twist. While many of the examples provided by the type designer show off the funky side of the font, thanks to the additional ligatures and alternative styles, you can always use the regular character sets. Either way, you’ll have a classy new font to use all over your website.

4. Happy Comic

Happy Comic is a font filled with personality. Looking at it makes me think of a goofy cartoon character or maybe even an older Adam Sandler movie. This would be a good font for branding lighthearted and humorous brands or publications.

5. Helsa Display

Helsa Display is a slim and compact serif. While serifs usually work pretty well for paragraph text, this one belongs in headlines and sub-headlines because of how thin the characters are. It also has a bit of a dark side (see the examples at the link to see what I mean), so reserve this font for boundary-pushing brands and personalities.

6. Lab Antiqua Variable

Lab Antiqua is a font that took years to create. The most recent release for this font family is called Lab Antiqua Variable. Like other variable fonts, Lab Antiqua will effortlessly transition through a range of font sizes without losing the characteristics that make this serif font so unique.

7. Monomorium

Monomorium is a monospaced typeface with open apertures and a flowing style. In addition, this quirky font comes with additional ligatures, stylistic alternates, parentheses, and more, depending on how fun or buttoned-up you want it to look.

8. Neumond

Neumond is a serif font that pushes the boundaries of legibility. This font gives you the ability to equip the characters with razor-sharp lines, overlap the letters, and push them towards extreme angles. If you have a brand that’s challenging the norm, a font like this that does the same will go really well with it.

9. Pratico Slab UI

Pratico Slab UI is a slab serif font that would add strength and character to the text of a website. You can also experiment with the weight and size if you’re looking for a not-so-boring but highly legible header font.

10. PT Nature

PT Nature is an exciting collection of script fonts. While they all technically belong to the PT Nature family, each font is modeled after different people’s handwriting. So this font family could be really useful if you use a lot of script fonts in your work. Or if you want to make one site and brand look like it has multiple personalities.

11. Rosehot Typeface

Rosehot Typeface is a pretty font that straddles the line between serif and sans serif. With its elegant curves, unexpected twists, and additional angles, this font would beautifully elevate designs for high-end retailers, fashionistas, and others with luxury offerings or services.

12. Shorai Sans

Shorai Sans is a sans serif font inspired by both calligraphic brushstrokes as well as geometric outlines. You can use it to style Latin text as well as Japanese. The font’s creators suggest pairing it with Avenir Next for greater harmony in your designs.

13. Shoutyperson

Shoutyperson is a bold all-caps font. Because of the grungy, stenciled style of the font, it’s not really applicable for many projects. That said, Shoutyperson would be an effective font choice for military, ammunition companies, or brands or personalities associated with a strict, regimented lifestyle (like personal trainers).

14. Simple Farmhouse

Simple Farmhouse is a basic handwriting font that’s highly legible. It resembles the style of writing you’d use to jot down notes on a whiteboard or in a notebook, so it would work well for brands that want to convey a casual and low-key vibe.

15. Sweet Pancakes

Sweet Pancakes is a fun font with full-bodied characters. Most of the examples provided frame the font against food, so this could be used on restaurant websites or food blogs. However, that’s not to say it couldn’t be used elsewhere. It’s a lighthearted and easy-to-read font, so it could just as well be used to style websites and branding for companies and personalities with a bubbly personality and/or positive mission.

Source

The post 15 Best New Fonts, April 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

How to Scale Your Design Process and Improve Handoff

,

It’s something every design team dreams about – a better design process and handoff procedure. Your design team is not alone if you are looking for a better solution.

Imagine what your workflow would look like if you could forgo the struggles of image-based technology, design and handoff with accurate components that have interactive features. Projects in the design phase will look more like final products and, most importantly, interact like final products. 

Let’s imagine a new design process together.

Challenges of an Image-Based Design Process

Here’s what we all know – image-based design tools provide pictures of components in the visual form but lack the interactivity and conditions that exist in the end-product. There’s not a high level of functional fidelity there, and it can cause confusion among design teams and rework.

These tools require you to redraw the fundamental components and design with boxes and rectangles, which takes too much time and can create a disconnect between the design and development teams. 

Further, you don’t fully maximize the potential of a design system because of inconsistencies between code-powered systems that developers use and these image-based systems for designers. There’s an innate gap between maintaining the environments and creating consistency in components. 

The final and maybe most difficult challenge with an image-based design process is in usability testing. You just can’t test an image the way you can working components. If the prototype is not interactive enough, you lose valuable feedback in the testing process. Functional fidelity is a must-have design and development tool in 2022. 

Iress, market-leading financial software, had many of these same problems in its design system process. You can probably relate to its story, which includes a designer and engineer who aren’t entirely on the same page, hit the deadline and have to deliver, and then get customer feedback. The result was a lot of extra headaches and work. 

But there is a better way: Import all user interface components into a code-powered design system in sync with a design tool so that your team can work in harmony to build, scale, and handoff projects with ease. 

Scale Design With Accurate Components

Here’s what most design and development teams want en route to building products: Accurate components with built-in interactivity, states, and conditions. No redrawing boxes and rectangles; no trying to figure out what states and interaction should be.

And if you can do it with ten times the speed and agility? Now you’re really in business. 

“It used to take us two to three months just to do the design. Now, with UXPin Merge, teams can design, test, and deliver products in the same timeframe,” said Erica Rider, Senior Manager for UX at PayPal. “Faster time to market is one of the most significant changes we’ve experienced using Merge.”

The time and workflow savings come from the ability to maintain only one environment as a product team. Rather than image-based tools, a code-powered design system that will push updates to components as the design evolves is the modern way to work. This workflow can also eliminate duplicate documentation so that your team has a single source of truth for whole product teams. 

Now you can be more agile in the design process and scale. And as Rider hinted at, there is a solution already available in UXPin Merge. 

Scalability with accurate design components has other benefits as well. 

Teams can onboard people faster because the design system is in the design tool. There’s less searching for answers with drag and drop-ready building blocks. New team members will find more success and be more valuable to the team quicker due to fewer inconsistencies and errors. 

Testing also gets a boost as you scale with a single source of truth. You can actually create better usability tests with a high-fidelity, functional version of the prototype, allowing users to leave more valuable and detailed feedback that can improve your product in the early stages. 

Better Handoffs Start Here

As you imagine a better design process, take it one step further. Better handoffs are a goal for most teams. 

An interactive component-based design tool can eliminate the need for multiple iterations of the same meeting to explain how a prototype works. Everyone can see and interact with it for themselves with accurate, true components that ensure the prototype works the same as the product. 

Designers will feel more like their vision is making it into the final product, and developers have a better idea of how to work. Everyone has the exact same components written in code. Thanks to the single source of truth, devs can speed up as they build the product because they start with components that include production-ready code.

A typical design to developer handoff might have multiple steps: Create vector design elements, create a model for interactions, and then send the prototype with documentation. Not to mention the meetings that are required to make sure everyone is on the same page.

In a model with interactive component elements, the developer handoff is fast and easy; they create a prototype with true components and all the built-in properties. The developer copies the JSX code and pastes it into his tool to build the final product. All the component properties and their coded interactions already exist in the source code. This is possible because the source of truth is the code itself, the source code.

Quick Tool Solution and Technical Use

This solution to this common challenge is not somewhere in the future; it’s already here.

UXPin, a code-based design tool, has Merge technology, which allows you to bring all interactive components into UXPin. Then you can use your own, or the open-source library with the ready-made building blocks to get products ready faster.

Here are just a few of the things you can do with Merge by UXPin:

  • Integrate your developer’s storybook to use it as a single source of truth (works for all frameworks)
  • Import design system components from a dev’s Git repository, such as GitHub, Bitbucket, GitLab, or others (works with React)
  • Work with the built-in MUI library
  • Add the npm component package to UXPin on your own (no developer required)
  • Design with the confidence that your work can be ideally reflected by developers
  • Create and share a library of interactive components

Summary 

Say bye-bye to redrawing rectangles – build more accurate prototypes easier and end-products faster with Merge by UXPin.

Now is the time to solve one of your biggest design challenges while upgrading and scaling the design process and improving handoffs. 

Merge by UXPin is user-friendly and made for scalable projects of almost any size. The line between design and development blurs with quicker product release and a fully-interactive solution. Request access today.

 

[– This is a sponsored post on behalf of UXPin –]

Source

The post How to Scale Your Design Process and Improve Handoff first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Analyzing iMessage With SQL

,

SQLite is an often overlooked flavor of SQL engines. Some have suggested it is the most prolific SQL engine in existence due to its highly flexible nature and ability to run on almost any platform with limited resources. Unlike other SQL engines like MySQL, PostgreSQL, MSSQL, or Oracle, SQLite runs without a server. SQLite does not rely on a data directory or a constantly running daemon: a database is encapsulated in a single file.

SQLite and iMessage

iMessage is one of the most popular messaging platforms today, largely because it is built into iOS and Mac devices. Since its release, it has evolved significantly. But, at its core, it is simply an instant messaging platform. iMessage uses SQLite in the background to store relational data about messages, conversations, and their participants.

Source de l’article sur DZONE

/par