Next.js Authentication: Step-by-Step Implementation Guide

Next.js authentication involves verifying a user's identity within a Next.js application. This process ensures that users are who they claim to be, typically using credentials like a username and password. Next.js provides robust tools for implementing authentication, allowing developers to secure their web applications effectively.

In Next.js, the authentication flow usually begins with the user submitting their credentials through a login form. The application then verifies these credentials against stored user data. Successful authentication grants the user access to protected resources, while failed attempts result in an error message.

The const user object often holds the authenticated user's data throughout the session, ensuring only authenticated users can access certain parts of the application.

Importance of Secure Authentication in Web Applications

Secure authentication is critical for protecting both the user's data and the integrity of the web application. Implementing robust user authentication methods helps prevent unauthorized access, ensuring that sensitive information remains secure.

In modern web applications, it's crucial to manage user sessions effectively. This involves using session management techniques to maintain the user's state across multiple requests, typically through cookies or tokens.

Overview of Authentication and Authorization

Authentication and authorization are two distinct but related concepts in web security. Authentication verifies the user’s identity, ensuring they are who they claim to be. Authorization, on the other hand, determines what an authenticated user is allowed to do within the application. This involves setting up access control mechanisms to ensure that only authorized users can access specific resources or perform certain actions.

In Next.js, you can implement various authentication strategies, such as OAuth, credentials-based login, and passwordless authentication, depending on the application’s needs. To implement authentication, you can use libraries like NextAuth.js and Passport.js, which provide robust solutions for handling authentication and authorization.

Each strategy involves a unique authentication flow tailored to different security requirements and user experiences. For example, OAuth allows users to log in using their social media accounts, while credentials-based login requires them to enter a username and password.

Setting Up Authentication in Next.js

Installing and Configuring Next.js

To begin with Next.js authentication, you need to have a Next.js application set up. If you don’t have one already, you can create a new Next.js project using the following commands:

1npx create-next-app@latest my-next-app
2cd my-next-app

​

After creating your project, navigate into the project directory. Next, install the necessary dependencies for authentication. One of the most popular libraries for authentication in Next.js is next-auth.

1npm install next-auth

​

Next, create a configuration file for Next.js. This js file can be named next.config.js and placed in the root directory of your project. Here, you can configure various settings for your Next.js application:

1// next.config.js
2module.exports = {
3  reactStrictMode: true,
4}

​

Creating the Auth Directory

Organize your authentication-related code by creating an auth directory. This directory will hold the configuration and API routes for handling authentication. Start by creating the necessary folders and files:

1mkdir -p src/auth
2touch src/auth/[...nextauth].ts

​

The [...nextauth].ts file will handle the dynamic API routes required for authentication. This is where you will configure and implement the authentication logic using next-auth.

Setting Up API Routes for Authentication

With Next.js, API routes can be used to handle various server-side functionalities, including authentication. Here's an example setup for the [...nextauth].ts file using next-auth:

1// src/auth/[...nextauth].ts
2import NextAuth from 'next-auth';
3import Providers from 'next-auth/providers';
4
5export default NextAuth({
6  providers: [
7    Providers.Credentials({
8      name: 'Credentials',
9      credentials: {
10        username: { label: "Username", type: "text" },
11        password: {  label: "Password", type: "password" }
12      },
13      authorize: async (credentials) => {
14        const user = { id: 1, name: 'User' }; // Replace this with your own user lookup logic
15        if (user) {
16          return user;
17        } else {
18          return null;
19        }
20      }
21    })
22  ],
23  pages: {
24    signIn: '/auth/signin',
25    signOut: '/auth/signout',
26    error: '/auth/error', // Error code passed in query string as ?error=
27    verifyRequest: '/auth/verify-request', // (used for check email message)
28    newUser: null // If set, new users will be directed here on first sign in
29  },
30  session: {
31    jwt: true, // Use JSON Web Tokens for session management
32  },
33  callbacks: {
34    async jwt(token, user) {
35      if (user) {
36        token.id = user.id;
37      }
38      return token;
39    },
40    async session(session, token) {
41      session.user.id = token.id;
42      return session;
43    }
44  }
45});

​

This configuration sets up a credentials provider, allowing users to log in using a username and password. The authorize function should be replaced with your own logic for verifying user credentials against stored user data. The session and jwt callbacks handle session data and token management.

Creating a Login Page

You'll need a login page where users can enter their credentials. Create a new file signin.tsx under the pages/auth directory:

1// pages/auth/signin.tsx
2import { signIn } from 'next-auth/react';
3
4export default function SignIn() {
5  const handleSubmit = async (event) => {
6    event.preventDefault();
7    const data = new FormData(event.target);
8    await signIn('credentials', {
9      redirect: false,
10      username: data.get('username'),
11      password: data.get('password')
12    });
13  }
14
15  return (
16    <form onSubmit={handleSubmit}>
17      <input name="username" type="text" placeholder="Username" required />
18      <input name="password" type="password" placeholder="Password" required />
19      <button type="submit">Sign In</button>
20    </form>
21  );
22}

​

This form captures the user's credentials and calls the signIn method from next-auth to handle the authentication flow.

Protecting API Routes

To protect specific API routes, you can use middleware to check the authentication status before allowing access. Here’s how you can create a middleware for protected routes:

1// src/middleware.ts
2import { withAuth } from 'next-auth/middleware';
3
4export default withAuth({
5  pages: {
6    signIn: '/auth/signin',
7  },
8});

​

Final Steps

Finally, ensure that your next.config.js includes the appropriate settings to support your authentication setup:

1// next.config.js
2module.exports = {
3  reactStrictMode: true,
4  serverRuntimeConfig: {
5    // Add your server runtime config here
6  },
7  publicRuntimeConfig: {
8    // Add your public runtime config here
9  },
10};

​

With these steps, you have set up a basic authentication system in your Next.js application, allowing users to log in and access protected routes.

Implementing Authentication Strategies

Using Authentication Providers

Integrating with Popular Authentication Providers

Using authentication providers like Google, GitHub, or Facebook can simplify the authentication process for your Next.js application. These providers offer OAuth-based authentication, which is both secure and user-friendly. Here's how to integrate popular authentication providers using next-auth.

First, install the necessary package:

1npm install next-auth

​

Then, create a configuration file for next-auth in your auth directory:

1// src/auth/[...nextauth].ts
2import NextAuth from 'next-auth';
3import Providers from 'next-auth/providers';
4
5export default NextAuth({
6  providers: [
7    Providers.Google({
8      clientId: process.env.GOOGLE_CLIENT_ID,
9      clientSecret: process.env.GOOGLE_CLIENT_SECRET,
10    }),
11    Providers.GitHub({
12      clientId: process.env.GITHUB_CLIENT_ID,
13      clientSecret: process.env.GITHUB_CLIENT_SECRET,
14    }),
15  ],
16  pages: {
17    signIn: '/auth/signin',
18  },
19  session: {
20    jwt: true,
21  },
22  callbacks: {
23    async jwt(token, user) {
24      if (user) {
25        token.id = user.id;
26      }
27      return token;
28    },
29    async session(session, token) {
30      session.user.id = token.id;
31      return session;
32    },
33  }
34});

​

Make sure to add the corresponding environment variables in your .env file:

1GOOGLE_CLIENT_ID=your-google-client-id
2GOOGLE_CLIENT_SECRET=your-google-client-secret
3GITHUB_CLIENT_ID=your-github-client-id
4GITHUB_CLIENT_SECRET=your-github-client-secret

​

This setup allows users to sign in with their Google or GitHub accounts, leveraging the OAuth authentication flow provided by these platforms.

Custom Authentication Solutions

In some cases, you might need a custom authentication solution tailored to your application's specific requirements. This can involve using a database to store user credentials and managing the authentication flow manually.

Here’s an example of implementing a custom credentials provider with next-auth:

1// src/auth/[...nextauth].ts
2import NextAuth from 'next-auth';
3import Providers from 'next-auth/providers';
4import { verifyPassword } from '@/lib/auth';
5
6export default NextAuth({
7  providers: [
8    Providers.Credentials({
9      name: 'Credentials',
10      credentials: {
11        email: { label: "Email", type: "text" },
12        password: { label: "Password", type: "password" }
13      },
14      authorize: async (credentials) => {
15        const user = await getUserByEmail(credentials.email);
16        if (user && await verifyPassword(credentials.password, user.password)) {
17          return user;
18        }
19        return null;
20      }
21    })
22  ],
23  session: {
24    jwt: true,
25  },
26  callbacks: {
27    async jwt(token, user) {
28      if (user) {
29        token.id = user.id;
30      }
31      return token;
32    },
33    async session(session, token) {
34      session.user.id = token.id;
35      return session;
36    },
37  }
38});

​

In this example, the authorize function checks the provided credentials against the stored user data, using a custom verifyPassword function to validate the password.

Building a Custom Login Page

Designing the Login Form

A custom login page can provide a more personalized user experience. Here’s how to design a basic login form in Next.js:

1// pages/auth/signin.tsx
2import { signIn } from 'next-auth/react';
3
4export default function SignIn() {
5  const handleSubmit = async (event) => {
6    event.preventDefault();
7    const data = new FormData(event.target);
8    await signIn('credentials', {
9      redirect: false,
10      email: data.get('email'),
11      password: data.get('password')
12    });
13  }
14
15  return (
16    <form onSubmit={handleSubmit}>
17      <input name="email" type="email" placeholder="Email" required />
18      <input name="password" type="password" placeholder="Password" required />
19      <button type="submit">Sign In</button>
20    </form>
21  );
22}

​

This form captures the user's email and password, and on submission, it calls the signIn function from next-auth to handle authentication.

Handling User Credentials

When handling user credentials, it’s crucial to ensure they are securely processed and stored. Passwords should always be hashed before storing them in the database. Here’s an example using bcrypt:

1// lib/auth.js
2import bcrypt from 'bcryptjs';
3
4export async function hashPassword(password) {
5  const hashedPassword = await bcrypt.hash(password, 12);
6  return hashedPassword;
7}
8
9export async function verifyPassword(password, hashedPassword) {
10  const isValid = await bcrypt.compare(password, hashedPassword);
11  return isValid;
12}

​

When a user submits their credentials, the application should verify the provided password against the stored hashed password. This ensures that even if the stored data is compromised, the original passwords are not exposed.

Managing User Sessions and Data

Session Management in Next.js

Session management is a crucial aspect of maintaining user state across multiple requests in a web application. In Next.js, you can handle sessions using various strategies, such as cookies, JSON Web Tokens (JWT), or server-side sessions.

Storing Session Data

To store session data in Next.js, you can use cookies or JWTs, both of which can securely keep track of user sessions. Here’s an example using next-auth with JWTs:

1// src/auth/[...nextauth].ts
2import NextAuth from 'next-auth';
3import Providers from 'next-auth/providers';
4
5export default NextAuth({
6  providers: [
7    Providers.Credentials({
8      name: 'Credentials',
9      credentials: {
10        username: { label: "Username", type: "text" },
11        password: { label: "Password", type: "password" }
12      },
13      authorize: async (credentials) => {
14        const user = await getUserByUsername(credentials.username);
15        if (user && verifyPassword(credentials.password, user.password)) {
16          return user;
17        }
18        return null;
19      }
20    })
21  ],
22  session: {
23    jwt: true,
24  },
25  callbacks: {
26    async jwt(token, user) {
27      if (user) {
28        token.id = user.id;
29      }
30      return token;
31    },
32    async session(session, token) {
33      session.user.id = token.id;
34      return session;
35    },
36  }
37});

​

In this setup, JWTs are used to manage session data. The jwt callback handles the token, while the session callback includes the user's information in the session data.

Managing Database Sessions

For more robust session management, you might want to store session data in a database. This allows for persistent sessions and easier management of user data. Here’s an example using a database to store sessions with next-auth:

1// src/auth/[...nextauth].ts
2import NextAuth from 'next-auth';
3import Providers from 'next-auth/providers';
4import Adapters from 'next-auth/adapters';
5
6const databaseUrl = process.env.DATABASE_URL;
7
8export default NextAuth({
9  providers: [
10    Providers.Credentials({
11      name: 'Credentials',
12      credentials: {
13        username: { label: "Username", type: "text" },
14        password: { label: "Password", type: "password" }
15      },
16      authorize: async (credentials) => {
17        const user = await getUserByUsername(credentials.username);
18        if (user && verifyPassword(credentials.password, user.password)) {
19          return user;
20        }
21        return null;
22      }
23    })
24  ],
25  database: databaseUrl,
26  session: {
27    jwt: false,
28  },
29  callbacks: {
30    async session(session, user) {
31      session.user = user;
32      return session;
33    },
34  },
35  adapter: Adapters.TypeORM.Adapter(
36    databaseUrl,
37    {
38      models: {
39        User: Adapters.TypeORM.Models.User,
40      },
41    }
42  ),
43});

​

This configuration uses TypeORM to store session data in a database, ensuring sessions persist across server restarts and providing a more scalable solution.

Handling User Data

Proper management of user data is essential for maintaining security and providing a seamless user experience. This involves setting up access control mechanisms and defining user permissions.

Access Control and User Permissions

Access control ensures that users can only access resources they are authorized to use. In Next.js, you can implement access control using middleware or server-side logic to check user roles and permissions. Here’s an example of how to implement basic access control:

1// src/middleware.ts
2import { withAuth } from 'next-auth/middleware';
3
4export default withAuth({
5  pages: {
6    signIn: '/auth/signin',
7  },
8  callbacks: {
9    authorized: ({ token }) => {
10      // Example: Only allow users with the role 'admin' to access /admin routes
11      return token?.role === 'admin';
12    }
13  }
14});

​

This middleware checks if the user has the required role before granting access to protected routes.

Admin Privileges and Authorized Users

Admin privileges can be managed by defining roles and permissions within your application. Here’s how you can handle admin-specific access:

1// src/auth/[...nextauth].ts
2import NextAuth from 'next-auth';
3import Providers from 'next-auth/providers';
4
5export default NextAuth({
6  providers: [
7    Providers.Credentials({
8      name: 'Credentials',
9      credentials: {
10        username: { label: "Username", type: "text" },
11        password: { label: "Password", type: "password" }
12      },
13      authorize: async (credentials) => {
14        const user = await getUserByUsername(credentials.username);
15        if (user && verifyPassword(credentials.password, user.password)) {
16          if (user.role === 'admin') {
17            user.isAdmin = true;
18          }
19          return user;
20        }
21        return null;
22      }
23    })
24  ],
25  callbacks: {
26    async jwt(token, user) {
27      if (user) {
28        token.id = user.id;
29        token.isAdmin = user.isAdmin || false;
30      }
31      return token;
32    },
33    async session(session, token) {
34      session.user.id = token.id;
35      session.user.isAdmin = token.isAdmin;
36      return session;
37    },
38  }
39});

​

In this example, admin users are identified during the authorization process, and the isAdmin flag is set in the token and session. This allows you to easily check for admin privileges in your application.

Protecting Routes and Access Control

Accessing Protected Routes

Protecting routes in a Next.js application is essential to ensure that only authenticated users can access certain parts of your application. This involves checking the user's authentication status and redirecting them if they are not authenticated.

Redirecting Unauthenticated Users

To protect routes and redirect unauthenticated users, you can use middleware in Next.js. Middleware allows you to run code before a request is completed, making it perfect for authentication checks. Here's an example using next-auth middleware:

1// src/middleware.ts
2import { withAuth } from 'next-auth/middleware';
3
4export default withAuth({
5  pages: {
6    signIn: '/auth/signin',
7  },
8});

​

In this setup, any unauthenticated user trying to access a protected route will be redirected to the /auth/signin page.

Implementing Access Control

Access control ensures that only users with the appropriate permissions can access certain routes. You can implement access control by checking the user's role within the middleware. Here’s an example:

1// src/middleware.ts
2import { withAuth } from 'next-auth/middleware';
3
4export default withAuth({
5  pages: {
6    signIn: '/auth/signin',
7  },
8  callbacks: {
9    authorized: ({ token }) => {
10      // Example: Only allow users with the role 'admin' to access /admin routes
11      return token?.role === 'admin';
12    }
13  }
14});

​

In this example, only users with the 'admin' role can access the /admin routes. Other users will be redirected to the sign-in page.

Managing Admin Users and Privileges

Managing admin users and their privileges is crucial for maintaining the security and proper functioning of your application. Admin users typically have higher privileges and can perform actions that regular users cannot.

Setting Up Admin User Access

To set up admin user access, you first need to identify admin users during the authentication process. Here’s how you can modify your authentication configuration to set up admin users:

1// src/auth/[...nextauth].ts
2import NextAuth from 'next-auth';
3import Providers from 'next-auth/providers';
4
5export default NextAuth({
6  providers: [
7    Providers.Credentials({
8      name: 'Credentials',
9      credentials: {
10        username: { label: "Username", type: "text" },
11        password: { label: "Password", type: "password" }
12      },
13      authorize: async (credentials) => {
14        const user = await getUserByUsername(credentials.username);
15        if (user && verifyPassword(credentials.password, user.password)) {
16          if (user.role === 'admin') {
17            user.isAdmin = true;
18          }
19          return user;
20        }
21        return null;
22      }
23    })
24  ],
25  callbacks: {
26    async jwt(token, user) {
27      if (user) {
28        token.id = user.id;
29        token.isAdmin = user.isAdmin || false;
30      }
31      return token;
32    },
33    async session(session, token) {
34      session.user.id = token.id;
35      session.user.isAdmin = token.isAdmin;
36      return session;
37    },
38  }
39});

​

This code sets the isAdmin flag during the authentication process, which you can then use to check for admin privileges throughout your application.

Handling Unauthorized Users

Handling unauthorized users involves ensuring that users without the required permissions cannot access certain routes or perform certain actions. Here’s an example of how you can handle unauthorized users in a protected route:

1// pages/admin/index.tsx
2import { getSession } from 'next-auth/react';
3import { useEffect } from 'react';
4import { useRouter } from 'next/router';
5
6export default function AdminPage() {
7  const router = useRouter();
8
9  useEffect(() => {
10    const securePage = async () => {
11      const session = await getSession();
12      if (!session || !session.user.isAdmin) {
13        router.push('/auth/signin');
14      }
15    };
16    securePage();
17  }, [router]);
18
19  return (
20    <div>
21      <h1>Admin Dashboard</h1>
22      {/* Admin content */}
23    </div>
24  );
25}

​

In this example, the getSession function checks if the user is authenticated and has admin privileges. If the user is not an admin, they are redirected to the sign-in page.

Enhancing Authentication Security

Multi-Factor Authentication

Multi-Factor Authentication (MFA) adds an additional layer of security by requiring users to provide two or more verification factors to gain access to a resource. Implementing MFA can significantly reduce the risk of unauthorized access.

To implement MFA in a Next.js application using next-auth, you can integrate with an external provider like Auth0, which supports MFA. Here's an example:

1// src/auth/[...nextauth].ts
2import NextAuth from 'next-auth';
3import Providers from 'next-auth/providers';
4
5export default NextAuth({
6  providers: [
7    Providers.Auth0({
8      clientId: process.env.AUTH0_CLIENT_ID,
9      clientSecret: process.env.AUTH0_CLIENT_SECRET,
10      domain: process.env.AUTH0_DOMAIN,
11    }),
12  ],
13  callbacks: {
14    async jwt(token, user) {
15      if (user) {
16        token.id = user.id;
17        token.mfaEnabled = user.mfaEnabled;
18      }
19      return token;
20    },
21    async session(session, token) {
22      session.user.id = token.id;
23      session.user.mfaEnabled = token.mfaEnabled;
24      return session;
25    },
26  }
27});

​

In this setup, you can configure Auth0 to enforce MFA for user accounts. More detailed configurations can be found in the Auth0 documentation.

Error Handling and User Feedback

Displaying Error Messages

Providing clear error messages helps users understand what went wrong and how to rectify it. In next-auth, you can customize error handling by defining error pages and displaying specific messages based on the error type.

1// pages/auth/error.tsx
2import { useRouter } from 'next/router';
3
4export default function ErrorPage() {
5  const router = useRouter();
6  const { error } = router.query;
7
8  const errorMessages = {
9    Signin: 'Try signing in with a different account.',
10    OAuthSignin: 'Error in OAuth Signin.',
11    OAuthCallback: 'Error in OAuth Callback.',
12    OAuthCreateAccount: 'Error creating OAuth account.',
13    EmailCreateAccount: 'Error creating email account.',
14    Callback: 'Error in callback.',
15    EmailSignin: 'Error in email signin.',
16    CredentialsSignin: 'Error in credentials signin.',
17    SessionRequired: 'Please sign in to access this page.',
18    default: 'An unknown error occurred.',
19  };
20
21  return (
22    <div>
23      <h1>Authentication Error</h1>
24      <p>{errorMessages[error] || errorMessages.default}</p>
25    </div>
26  );
27}

​

This page displays user-friendly error messages based on the error type passed in the query string.

Managing User Interaction and Feedback

Providing immediate feedback on user actions improves the user experience. For example, showing a loading spinner while processing authentication or confirmation messages upon successful login helps keep users informed.

1// pages/auth/signin.tsx
2import { signIn } from 'next-auth/react';
3import { useState } from 'react';
4
5export default function SignIn() {
6  const [loading, setLoading] = useState(false);
7  const [message, setMessage] = useState('');
8
9  const handleSubmit = async (event) => {
10    event.preventDefault();
11    setLoading(true);
12    const data = new FormData(event.target);
13    const result = await signIn('credentials', {
14      redirect: false,
15      email: data.get('email'),
16      password: data.get('password')
17    });
18    setLoading(false);
19
20    if (result.error) {
21      setMessage('Login failed. Please check your credentials and try again.');
22    } else {
23      setMessage('Login successful! Redirecting...');
24    }
25  }
26
27  return (
28    <form onSubmit={handleSubmit}>
29      <input name="email" type="email" placeholder="Email" required />
30      <input name="password" type="password" placeholder="Password" required />
31      <button type="submit">{loading ? 'Signing in...' : 'Sign In'}</button>
32      {message && <p>{message}</p>}
33    </form>
34  );
35}

​

This example shows how to provide loading indicators and success/error messages based on the authentication result.

Best Practices for Secure Authentication

Preventing Unauthorized Access

To prevent unauthorized access, follow these best practices:

1. Use Strong Passwords: Enforce strong password policies and consider using password hashing algorithms like bcrypt.

2. Implement Rate Limiting: Protect your authentication endpoints from brute-force attacks by limiting the number of attempts a user can make in a given period.

3. Use HTTPS: Ensure all data transmitted between the client and server is encrypted by using HTTPS.

Ensuring Secure Session Management

Secure session management involves protecting session data and ensuring that sessions are properly maintained and terminated. Here are some practices:

1. Use Secure Cookies: Set the secure and HttpOnly flags on cookies to prevent unauthorized access.

2. Short Session Lifetimes: Limit the duration of sessions and require users to re-authenticate after a certain period.

3. Invalidate Sessions on Logout: Ensure that sessions are properly invalidated when users log out.

Here’s an example of setting secure cookies with next-auth:

1// src/auth/[...nextauth].ts
2import NextAuth from 'next-auth';
3import Providers from 'next-auth/providers';
4
5export default NextAuth({
6  providers: [
7    Providers.Credentials({
8      name: 'Credentials',
9      credentials: {
10        username: { label: "Username", type: "text" },
11        password: { label: "Password", type: "password" }
12      },
13      authorize: async (credentials) => {
14        const user = await getUserByUsername(credentials.username);
15        if (user && verifyPassword(credentials.password, user.password)) {
16          return user;
17        }
18        return null;
19      }
20    })
21  ],
22  session: {
23    jwt: true,
24    maxAge: 30 * 60, // 30 minutes
25    updateAge: 24 * 60 * 60, // 24 hours
26  },
27  cookies: {
28    sessionToken: {
29      name: `__Secure-next-auth.session-token`,
30      options: {
31        httpOnly: true,
32        sameSite: 'lax',
33        path: '/',
34        secure: process.env.NODE_ENV === 'production',
35      },
36    },
37  },
38});

​

This configuration sets the session token cookie with secure attributes and limits the session duration to 30 minutes.

By following these practices and integrating the above techniques, you can enhance the security of your authentication system in your Next.js application.

Conclusion

Implementing secure and efficient authentication in a Next.js application is essential for protecting user data and ensuring a smooth user experience. By leveraging tools like next-auth for integrating popular authentication providers, managing user sessions, and enhancing security through Multi-Factor Authentication and robust error handling, you can build a resilient authentication system.

Following best practices for preventing unauthorized access and ensuring secure session management further fortifies your application's defenses. By incorporating these strategies, you can provide a reliable and secure authentication experience for your users, enhancing the overall security and functionality of your web application.

Short on time? Speed things up with DhiWise!

Tired of manually designing screens, coding on weekends, and technical debt? Let DhiWise handle it for you!

You can build an e-commerce store, healthcare app, portfolio, blogging website, social media or admin panel right away. Use our library of 40+ pre-built free templates to create your first application using DhiWise.