Forem: ShinaBR2

SSO with Firebase Authentication

ShinaBR2 — Sun, 01 Dec 2024 01:15:14 +0000

See full article: https://docs.shinabr2.com/blog/sso-with-firebase-authentication

Firestore data modeling

ShinaBR2 — Sat, 07 Jan 2023 04:58:36 +0000

6 minutes read my original post here: https://sworld-docs.netlify.app/blog/firestore-data-modeling/

Firebase NoSQL database

ShinaBR2 — Sat, 03 Dec 2022 14:23:26 +0000

It was busy recently to me, I am lazy to copy again, please view the original article here: https://sworld-docs.netlify.app/blog/firebase-nosql-database

Headless UI audio player reactJS

ShinaBR2 — Sun, 20 Nov 2022 05:10:27 +0000

Many reacjt developers want to develop and publish npm packages for reusable, and so do I. Since the first few days working with reactjs, I feel it does not make sense to build a react UI library but depends on the UI framework.

The final npm package: https://www.npmjs.com/package/@shinabr2/life-core

Few concerns:

Why do I need to import material UI or the antd design just for using a library? If I am going to use another UI library like semantic, why does it break?
What if I want to control the rendered HTML output?
The library itself should be isolated by default and should just work as long as I import it into my code base.

With the release of react hooks, this problem now becomes easier to resolve. And here is my first headless UI react audio player component, it was a part of my personal project.

The implementation is quite simple since it took me around 2 hours to complete, but the typescript part took me 2 days and unresolved yet. I will get back to typescript sucks issue later.

For quick view the demo with awesome songs from Attack on Titan: https://stackblitz.com/edit/react-1ym6yv?file=src/App.js

Basic

The only required props is source of audio list. The only requirement for using is adding {...getAudioProps()} as props to your <audio> component.

const audioList = [
  {
    src: "https://res.cloudinary.com/shinabr2/video/upload/v1667828415/Public/Music/Japanese/Attack-on-Titan-Opening-1-Feuerroter-Pfeil-und-Bogen-Full-128-Linked-Horizon_1.mp3",
    name: "Guren No Yumiya",
    artistName: "Linked Horizon",
    image:
      "https://res.cloudinary.com/shinabr2/image/upload/v1667828561/Public/Images/artworks-000141088556-xy2nav-t500x500.jpg",
  },
  {
    src: "https://res.cloudinary.com/shinabr2/video/upload/v1667831555/Public/Music/Japanese/Shinzou_wo_Sasageyo__-_Linked_Horizon.mp3",
    name: "Shinzo wo Sasageyo",
    artistName: "Linked Horizon",
    image:
      "https://res.cloudinary.com/shinabr2/image/upload/v1667828561/Public/Images/artworks-000141088556-xy2nav-t500x500.jpg",
  },
];

const App = () => {
    const { getAudioProps } = useSAudioPlayer({ audioList });

    return (
        <div>
            <audio {...getAudioProps()} />
        </div>
    )
}

With your custom controls

Just use the playerState to determine the audio playing status, and the getControlsProps exposes all methods for your custom control like play, pause, prev, next, shuffle, change loop mode.

const audioList = [
  {
    src: "https://res.cloudinary.com/shinabr2/video/upload/v1667828415/Public/Music/Japanese/Attack-on-Titan-Opening-1-Feuerroter-Pfeil-und-Bogen-Full-128-Linked-Horizon_1.mp3",
    name: "Guren No Yumiya",
    artistName: "Linked Horizon",
    image:
      "https://res.cloudinary.com/shinabr2/image/upload/v1667828561/Public/Images/artworks-000141088556-xy2nav-t500x500.jpg",
  },
  {
    src: "https://res.cloudinary.com/shinabr2/video/upload/v1667831555/Public/Music/Japanese/Shinzou_wo_Sasageyo__-_Linked_Horizon.mp3",
    name: "Shinzo wo Sasageyo",
    artistName: "Linked Horizon",
    image:
      "https://res.cloudinary.com/shinabr2/image/upload/v1667828561/Public/Images/artworks-000141088556-xy2nav-t500x500.jpg",
  },
];

const App = () => {
    const {
    getAudioProps,
    getControlsProps,
    playerState
  } = useSAudioPlayer({ audioList });
  const { isPlay, isShuffled, loopMode, audioItem } = playerState;
  const {
    onPlay,
    onPrev,
    onNext,
    onShuffle,
    onChangeLoopMode
  } = getControlsProps();

    return (
        <div>
      <button onClick={onChangeLoopMode}>Loop</button>
      <button onClick={onPrev}>Prev</button>
      <button onClick={onPlay}>{isPlay ? 'Pause' : 'Play'}</button>
      <button onClick={onNext}>Next</button>
      <button onClick={onShuffle}>Shuffle</button>
            <audio {...getAudioProps()} controls />
        </div>
    )
}

API

The types for all inputs are quite simple as below

interface SAudioPlayerAudioItem {
  src: string;
  name: string;
  artistName: string;
  image: string;
}

enum SAudioPlayerLoopMode {
  None = "none",
  All = "all",
  One = "one",
}

interface SAudioPlayerConfigs {
  shuffle?: boolean;
  loopMode?: SAudioPlayerLoopMode;
}

interface SAudioPlayerInputs {
  audioList: SAudioPlayerAudioItem[];
  index?: number;
  configs?: SAudioPlayerConfigs;
}

// Using
useSAudioPlayer(inputs: SAudioPlayerInputs)

Are you ready for the future working style?

ShinaBR2 — Sat, 01 May 2021 03:09:40 +0000

It is easy to find a job where they need a senior developer. But I don't know why not many jobs need a professional developer in the description.

To be honest, I don't really know which is "senior developer", but for me, "senior developer" does not matter at all. "Professional developer" is the most important person you will need in life.

Don't believe it? I'll show you now my points.

Respect

This is the first thing I want to talk about, and the most important thing. Let's talk about how we work together nowadays.

For whole team communication, we usually have:

A task management tool like Jira.
An official chat tool like Slack.
Code versioning for developers like Git flow.

If you think they are enough, NOPE. We still miss one thing: a calendar.

The professional working style here where how a developer respects these above things.

Do you ALWAYS be on time for meetings?
Do you update JIRA tickets in real-time?
Do you consistently quick reply to slack messages?
Do you truly follow git-flow?

These behaviors are small but extremely valuable especially in the remote working style, or in teams where almost all members are in different time zones. For developers, people who not follow git-flow is terribly bad to me and they should be fired as soon as possible.

Without following the rules, a genius is just nothing.

So for this one, seniority seems does not matter, right?

Yourself or your team?

I want to talk about one behavior: direct messages in Slack instead of chatting in common channels.

There are some points that make this behavior unprofessional or even bad to me:

Everybody else can not have the information they talked about. Whenever we have related problems, nobody knows. Unfortunately, almost all communication issues come from here where we mismatch each other.
You can not distinguish what is your problem, and what is your whole team's problem. That means you do not understand your team enough.

Proactive

No need to talk every time, just need the right time, and always there. That's the definition of a proactive member.

Stop waiting for somebody else to make the job done. This is the kind of person you will never want to work together in your life. The seniority does not matter here again because they are good enough to resolve problems, but they chose to wait. This is really annoying and I believe, nobody willing to take this.

Another behavior of inactive developers is making assumptions without asking anything. They thought they can do everything, they keep silent, keep working but nobody knows what are they doing. Working with this style of people is kind of waiting for a bomber since we don't really sure what and when everything is broken. Sorry but this behavior has more impact than you thought.

TL;DR

The remote working style is our future. Communication nowadays is not only what you talk via the mouth, but also what you did with your team's tools.

Again, a senior developer does not matter when compared to a professional one. You can change from now with:

Respect your team calendar and strictly follow its rule.
Active update your working progress in JIRA (and Slack if needed).
Stop private messaging in Slack.
Stop waiting for somebody else to make your job done.
Stop assumption without asking

Cheers,

What should web developers avoid implementing

ShinaBR2 — Tue, 27 Oct 2020 07:19:21 +0000

Hi, I am a lazy frontend developer come from Vietnam, the man looking for original values.

Web development is complex with tons of things to do. Besides that, there are still something that we should not do it by our hand, nearly similar to reinvent the wheel.

Let's see my list for 2020 afterwards. This article is suitable for mid or above junior developers. Fresher or below junior developer should manually do because you will learn many things from that.

I have divided all issues into 3 different groups:

The first group contain all works that involve from both side backend and frontend, or even has impact to architecture.
The second group has smaller tasks where you can take much time to implement by yourself, but can do.
The last group is reinvent the wheel jobs.

The first group: try to avoid these tasks

Authentication

This is the first thing I MUST mention.

Problem with handling Authentication by yourself

Sign in, sign out, register, forgot password, etc is some very boring things that need to be done on almost websites. It is the most basic functionality that a website should have. But if you manually implement the authentication process, maybe you're wasting your whole team on this.

The reasons are:

There is no clear benefit from the user's point of view when this function is completed. What is the user actually need is a single button, and they get signed in after clicked it.
Authentication is complex and complicated also. For example, manually implement the algorithm for the JWT token, manage the token lifetime, invalidate the expired token, and so on might take a lot of time and effort.
Every system has the same logic for Authentication from the past decade. You do not need to spend your resources on a very old problem that has many existing great solutions.
Security issues might appear if your authentication process is not well handled.

So, in terms of the trade-off between team effort and the benefit, risk management, do not implement authentication by yourself.

Solution

There are many good solutions out there such as:

I do not see any use case till now that one of each above product can not resolve. Please let me know if I am going wrong here.

Authorization

If authentication is a key let somebody get in your house, authorization is a list of permissions you let them touch into something or go somewhere when they in. Compared to Authentication, Authorization is more complicated because it totally depends on specific business logic. In other words, you can not reuse the old authorization system in your previous project.

Solution

There are many good solutions out there such as:

Hasura is the best candidate in my opinion.
Auth0 is a good solution suite.
8base, but it is a full Backend-as-a-service.
Okta is also a good solution at my first look.

The second group: can do with much effort

This group has various kinds of problems that we already have a powerful solution. I have not much time to explain everything. The order of things does not matter. I have tried to not list many solutions it will take your time on the comparison.

Email management

The reason why I recommend using an existing solution because the common use cases: the admins want to have dashboards for email management, and they can do lots of things with email template, email marketing and so on.

Solutions:

SendGrid: not much thing to talk about, it just has everything you need.
Mailchimp is a good candidate for small business.

Upload file

Let me go straight forward:

We usually store media assets in cloud.
It takes much effort on validation, UX and assets management.

Solutions:

If you use a CDN like Cloudinary, use its upload widget instead.
Uploadcare as its name, works in almost use cases.

Analytics dashboard

Building a dashboard for analytics purpose is a generic use case. In fact, it is a crucial feature from product point of view.

Instead of manually connecting to data warehouse, parsing data into chart components, please forget these works. The same reason as Authentication.

Solutions:

Retool is a good candidate but its performance is not wonderful for me.
Appsmith is open source, still in development but I prefer it over Retool.
holistics.io is a powerful BI tool, perfect fit for enterprise.

Chat and Notification System

Chat, push message, notification system are complex jobs in terms of performance. Yes you can totally find out a tutorial like "building your own chat in minutes" or so, but almost them are just for high level consideration only.

Solutions:

Sendbird offers a good solution for chat, message and so on.
Intercom is kind of must-have for enterprise level.
Twilio also support phone call and more.

The last group: Reinvent the wheel jobs

Like the title, sometimes if you try to do something in the below list, you are almost waste your life:

Build your own custom UI components. MaterialUI is the most customizable UI framework. On the other side, I highly recommend NOT to try to customize Antd.
Build dashboards interface from scratch. There are tons of admin template out there.
Build your own custom code generator. Depends on your actual business, but in most cases, you do not need it at all. Take a look at how Hasura did, you will see the point.

Dear my beloved readers

"Focusing on business logic" is the only thing I want to share if you are a developer. Not only your time, it is also how we could make better product.

Cheers and happy coding!

Race condition in React: conclusion

ShinaBR2 — Sun, 18 Oct 2020 07:09:02 +0000

Hi, I am a lazy frontend developer come from Vietnam, the man looking for original values.

There are so many problems that developers should not manually resolve nowadays. I will list of in another article. One of them is race condition.

Not only in ReactJS, race condition is a term used for an undesired situation when a single "resource" has been access at the same time from many "sources". "Sources" can be HTTP request, user, whatever, and the same for "resource". Let's think it easy as a sender and receiver.

Scenario

In JavaScript world, you need to face lots of problems caused by only one thing: asynchronous. The race condition is just one of them. In fact, we need to send lots of asynchronous API requests and know neither how long does each take nor the order of results.

Let say we have to call two request to get active product and update the result to the state with a condition: we do not need and also do not want to wait the second request has been made after the first has completed. You probably know this is not a rare case nowadays. We want, as soon as one of each result received, we take it and store into the state.

Please note that async/await or React-hook themselves do not resolve this problem. They are just a syntax to write your code, not the solution. You can read more from Dan Abramov article.

The solutions

There are three different solution levels for this scenario, from the basic to advance:

Writing by your hand
Use a middleware like Redux-saga.
Use GraphQL and Apollo

Writing by your hand

I highly recommend NOT using this way. The idea is simple: we need to cancel the first request. A great article you should take a look at this medium article. Do not need to duplicate his words.

Use a middleware like Redux-saga

Redux-saga is a popular library in React world in the past several years. It does not only resolve the race condition problem, it also helps you manage the asynchronous calls better.

I think do not need to talk more about Redux-saga now, almost React developers has great experience with it. But for me in 2020, using Redux and Redux-saga is a good signal to show that your code base will become messy. Redux is painful, it is not only my thought.

"Don’t use Redux if it’s painful (React doesn’t force you to). Not sure I understand how this relates to WCs".
-- Dan Abramov
https://twitter.com/dan_abramov/status/959225731019694080

Use GraphQL and Apollo

I have surprised recently when somebody asks me how to resolve race condition issue. Some seconds later, I realized that I do not need to resolve it for very long time (with Apollo Client helps). Long enough to forget I need to care about that problem.

This approach based on the core GraphQL. Like I said many times before, GraphQL is a revolution. But not like two previous approaches, you do not need to change whole infrastructure to resolve race condition problem. So in fact, you may need to consider when applying GraphQL into current existing code base because it changes everything.

Back to our main problem, from the beginning of using Apollo-client, it helps me reduce tons of time for considering many problems like state management, middleware, race condition and so on. A great article on medium has clearly explained everything you need.

Conclusion

It is 2020 now. There lots of things you need to learn in your developer journey. However, manually implementing the solution for problems like race condition is not a good thought. See you in the next article where I can list out all things a developer should do, and should not, too.

Thanks for your valuable reading time!

My Software Checklist

ShinaBR2 — Fri, 25 Sep 2020 01:31:57 +0000

This is the list of software need to be installed after installing Windows 10. Just for myself only, not an awesome article you usually see. Note that the only reason for using Windows is playing games, not for development. And all below things is enough for frontend development.

Utils

Google Chrome
Unikey (for Vietnamese only)
Slack
Winrar

Developer tools

MUST HAVE

Git
Node Version Manager (nvm)
Fork is a Git GUI client.
Yarn
Sublime text with the following packages:
- Babel
- Color Highlight
- DocBlockr
- JsPrettier
- SidebarEnhancements
- SublimeLinter + SublimeLinter-eslint
PuTTy

Nice to have

Axure is a tool for prototyping, mockup.
cmder is a portable terminal for windows, just install once, everywhere except disk C.

Relax

Steam

Terrible Apps

But sometime you will need because there are still some sucks reason that I don't want to list out.

Skype
Microsoft Office
TypeScript

User Story Mapping in practical way

ShinaBR2 — Wed, 23 Sep 2020 15:26:44 +0000

Hi, I am a lazy frontend developer come from Vietnam, the man looking for original values.

This is one of the series about User Story Mapping. You may take a look at my previous article about its concepts, basically are:

User Story Mapping help us easier to focus on prioritize work.
Everything in User Story Mapping is based on user perspective.

I also have mentioned that we need to tool to visualize these things. Fortunately, I found a good JIRA plugin. You can find all the references at the last section of this article.

Let's go to the first part to understand why User Story Mapping perfectly fit with Agile.

User Story Mapping with Agile

I assume that you have already known about Agile. We heard lots of teams and companies use Agile nowadays. I will list some basic notable benefits from Agile:

Breaking down very large project into small pieces to make easier to do everything from develop, testing and deployment. In other words, better product quality.
Focus on users.

Agile is great! But all we have known, in the large project, the "product backlog" is terrible long. That is the reason why User Story Mapping helps and it perfectly fit with above Agile benefits:

Each stage of development process can be mapped to a user goal in User Story Mapping.
User Story Mapping based on user perspective or in other words: "persona".

I will take a very common use case for web development as example. We want to build an e-commercial site. Let say we have two high level functions:

Login, logout, etc.
Buying or selling some products.

Next section is the practical way to work with User Story Mapping on JIRA. I assume that you have already known some basic terms in JIRA like "epic" and "ticket".

Visualization of User Story Mapping in JIRA

Creating a visualization of User Story Mapping basically follow these steps:

Create "persona" to understand which kind of requirement of each kind of user.
Define user goals
Divide all goals into smaller pieces and prioritize them

Please take a look at my result screenshot for a demo project I have created. This process should take time, of course.

Please tell me your first impression about this look and feel :) I really want to hear that you love it like me.

We have some rules for this tool based on User Story Mapping concepts:

Top row defines all user goals. From left to right is the user's narrative flow. In other words, from left to right is the happy case from user perspective to achieve a meaning result. In above picture, we have for example three goals are "Manage User" (login/logout/etc), "Buy a product" and "sell a product".
Second row define steps mapped to an "epic" in JIRA. This plugin also allow me to collapse all epics into one group. You can see I have grouped epics in "buy a product" and "sell a product" goals which shown the total number are 4 and 5 accordingly.
The last down part are the tickets, the smallest piece need to be done to perform "epic". You can see this plugin help me allow to create the milestones, release management, filtering tickets and so on. In this example, we have 14 for "buy a product" goal and 8 tickets for "sell a product" goal.

You can manage "personas" from the near top right button, next to the zoom button group.

Of course, you can add many goals, many tickets if you want. But I think, the shorter goals, the better visualization. The more tickets, the higher pressure.

This article is aimed to show you the practical look and feel of User Story Mapping, you can give it a try. This plugin is good enough for me, I am crazy like how it looks. But I found something should be better to be improved:

You need to learn "JQL" a bit. It is a language that helps you create the filters like pivot tables in Excel. It is easy if you are familiar with Data Analyst tools.
Some minor bugs on UI, does not matter if you are not a perfectionist like me.
I can not find out the way to feedback in two minutes. Not joke at all. I am an advanced user with having good sense of UX and understanding how important of user feedback is. Two minutes for me, is a notable time.
No onboarding process for a new user like me. DO NOT underestimate this thing. It is one of crucial things to keep your valuable users.

That's all. Thank you for your time, thank you for all of you guys reading this and see ya on next articles.

Related References

Uniqueness

ShinaBR2 — Thu, 17 Sep 2020 14:27:53 +0000

Hi, I am a lazy frontend developer come from Vietnam, the man looking for original values.

When start writing this article, I feel a bit hard to choose the
correct tags. Because this term "uniqueness" effects not only in programming but also in everything in our industry, or even in human life. I will show you now.

The Importance of Uniqueness thinking

Let's talk about our programming adventure first. We all know there are lots of problems that we faced. We need the core concepts, we need the design patterns, for what? - For resolving some specific problems? No, actually not. We need them because they are our light in all day long, hard but interesting adventure.

But have you ever think about one rule of thumb of those concepts, design patterns? One thing can rule them all?

My opinionated answer is the "uniqueness".

Uniqueness in programming

One of my favorite quotes in programming is:

There are only two hard things in Computer Science: cache invalidation and naming things.

-- Phil Karlton

It is okay if you have never heard about that. As soon as you realized these two things, the stronger thinking you have.

I considered this quote for many years. Because I am too lazy to remember two things, I want to figure out only one thing, one thing can lead to them, that is uniqueness. I realized long time ago before able to writing this article.

Why uniqueness can lead to two these things?

First, one hard step to achieve caching is defining cache key. Because it is a key, it needs to be unique.
Second, naming things, the name should be unique in current "scope". The term "scope" is different in different programming languages, but the core idea is the space that a variable has its meaning.

So I can think, if I can resolve uniqueness problem, all the remaining things should be easy. That is a good answer for somebody lazy like me.

Some other easy to see example to show how important of uniqueness is:

Primary key in database. All we already known.
Key for each item in a list. If you are working with React, please refer to this to see why it is so important.
Global variable name. If you have worked with jQuery, you will understand why $ need to be unique (back to naming things, back to unique again).
Lots of algorithms were born to resolve one problem: generate a unique string.
Identity: every user need to be identified right? And we need a unique id for it correct?
All other keys.

Of course please feel free if you find any other case that we need to make a thing unique.

I hope you can see the feeling I had about this single term. Now we go to the next section.

Uniqueness in everything

Like I said above, not only in programming, the uniqueness should be also a great impact in your human life.

The answer is simple, but actually not easy to do: because all of us, want to be unique among other people.

In an interview, every single person in us, want to be the best candidate. This actually mean we need to be unique among the others.
In our company, we strongly need to be unique, nobody wants people easy to find another one replace me.
In all of our relationships, we indeed need that unique thing.

These are enough for me. One thing, rule all other things.

So ...

How can I think uniqueness

In programming first, you can try to think about something that I mentioned in the first part before considering other problems. You may think those are easy. Yes, but if you practice it enough, you will easy to see the core of almost problems you face. Always think about uniqueness, how to make something, some object unique, how to identify an object or variable and so on.

In our human life, it is totally depends on you. But somehow similar to programming, you will become more brilliant. A good example is, how to guide a tourist to follow the right way? (You might need to find out some *** thing).

That's all! Thanks for your valuable time. Love ya and see you guys in next articles.

@shinabr2

Easy to get started with User Story Mapping

ShinaBR2 — Sun, 13 Sep 2020 11:35:03 +0000

Hi, I am a lazy frontend developer come from Vietnam, the man looking for original values.

In my developer life, I faced many problems, but till now, I think, the most critical problem for every team, every single product is “communication”. Unfortunately, the simple word “communication” seems not be easy as it is. And worse thing is, not many people understand the easy word “communication” in the same way. Today, I want to focus to one of those problems, task management.

Understanding the problem

I believe that almost people in this fancy industry has at least one time facing this scenario: they understand neither what actually be done nor what should they do with a task. The same for other teammates, they want to understand, but no way can achieve.

In the project management perspective, we have some methodologies, such as Waterfall, Scrum, etc. They were invented to try to resolve my above problem at high level. At the lower level, the actually method that developers like us had worked with (also for designers and every other teammate), is nothing more than an incredible long list of tasks.

Almost people are lazy to read, especially that above long list. Lots of redundant information there. In my point of view, it is one of the best ways to waste human resources. I do not think hiring a good person and told them what to do is a good strategy. I will let they do the best they can, and tell me the result instead.

Come back to above long list, what I am going to tell, User Story Mapping, is a good way to “transform” that list into another visual form, easy to focus.

I think, focusing, is everything we need for task management. In other words, with the old long list, nobody knows what is higher priority, which is not. That is the core problem here. Okay, so if we know the problem, easy to find the answer out, right?

Now, the solution

Let’s take a look at my below image (I spent about 5 minutes to draw using Microsoft paint). This is the very basic and simplest visual form of User Story Mapping concept. No need fancy words to make people understand.

I do not think I need to say more, is above image easy to get? So let say we have three wanted features are A, B, C. You might guess, the purple rounded rectangles mean big tasks need to be done to achieve the target feature which is above them, correct! Then other remaining rounded rectangles mean a task (that actually a task which developers like us work on).

So take more focus on the order of features, from left to right, it does not need to be mean the time. It is the order to make something meaning for the users. I believe, this is the only thing I want to talk in this overall talk.

Pros and cons

Now, take a second to consider why this visual form can help, especially in team communication (I think, you already have your answer now):

Now you are able to see the top priority thing to do. In case of above picture, that is feature A, the one has most emphasize color, on the top left. Remember the word “focus” I mentioned before?
The more important thing is, everybody now can understand the relation between their current work to the others, and to the overall project. In other words, it does not matter who you are, developers, business analyst, project manager, or even stakeholders, you can clearly see how everything is planned.

Please note, my picture, is a very basic concept, you can be creative to create more complex rules, filters and so on. There are many tools support you to do so. Understanding the core concept is the thing I want to talk about. Now the next part, find out the cons of User Story Mapping.

Follow that basic concept, we can figure out:

User Story Mapping should be short. You do not need to see thousands of wanted features. In the contrast, thousands of tasks is a very general scenario.
Keep the User Story Mapping updated!!! You know, a single task now be related to some people, not only one.
You need an extra tool for that, of course. We will talk about this in later articles.

Conclusion

I hope you are enjoyed my article. Actually all things I have done is just an image. You can have a deeper look about User Story Mapping via this great article. Every feedback should be highly appreciated. See you in next article about “how User Story Mapping perfectly fit in Agile”.

Do web users like "dark mode"?

ShinaBR2 — Mon, 03 Aug 2020 09:52:42 +0000

Like the title. I wonder because I have added dark mode by default for my website, and seems still somebody doesn't like that.
How do you guys think and have experience with that?