DEV Community: walerick

Mobile Development Platforms and Arcitecture patterns

walerick — Sun, 30 Jun 2024 22:34:15 +0000

We have different platforms that programmers use to develop scalable and efficient projects for mobile. Below are different mobile development patterns and their usefulness

Native Development : There are two categories for these platforms namely

IOS- can bedeveloped with swift or objective-c in Xcode.
Android - can be developed using kotlin or Java in Android Studio.

Cross-Platform Development: There are quite a few platforms under this category namely

Flutter- Uses Dart Language.
React Native- Uses Javascript and React.
Xamarin - Uses C# and .NET
Ion - Uses simple web technologies (html, Css and Js).

Hybrid Development :

Cardova - Uses Html, CSS and JavaScript.
Capacitor - Modern alternative to Cardova.

Common Software Arcitecture Pattern with their Pros and Cons

MVC(Model-View-Controller):

Model: Manages data and business logic.
View: Manages the display and user interface.
Controller: Acts as an intermediary between Model and View, handling user input and updating the view accordingly.

Pros:
Separation of Concerns: Clear division between the application's data, UI, and logic.
Reusability: Models and Views can be reused across different parts of the application.

Cons:

Overhead in Small Applications: For simple apps, MVC can add unnecessary complexity.
Complex Controller Logic: Controllers can become overloaded with logic, leading to "Massive View Controller" in iOS development.

MVP (Model-View-Presenter) :

Model: Manages the data and business logic.
View: A passive interface that displays data and routes user interactions to the Presenter.
Presenter: Handles all the UI logic and communicates between Model and View, making the View more passive.

Pros:

Improved Testability: Presenters can be tested independently from the Views, enhancing unit test coverage.
Decoupled View Logic: Views are simpler and more focused on rendering data, reducing the risk of complex, monolithic components.
Flexible Views: Easier to swap out or change Views without affecting business logic.

Cons:

Boilerplate Code: Can lead to a significant amount of boilerplate, especially in large applications.
Presenter Complexity: Presenters can become overly complex as they take on more responsibilities.
Maintenance Overhead: Managing interactions between multiple Presenters and Views can become cumbersome.

MVVM (Model-View-ViewModel)

Model: Manages data and business logic.
View: Handles the display and binds to properties exposed by the ViewModel.
ViewModel: Acts as a mediator between Model and View, exposing data and handling most of the logic.

Pros:

Two-Way Data Binding: Enables automatic synchronization between the View and the ViewModel, reducing the need for boilerplate code.
Enhanced Testability: ViewModels can be tested independently of the Views, promoting better test coverage.
Separation of Concerns: Clearly separates UI logic from business logic, making the code more maintainable.

Cons:

Complex Data Binding: Managing data binding can become complex and difficult to debug, especially in larger applications.
Performance Overhead: Extensive use of data binding may lead to performance issues due to frequent UI updates.
Steeper Learning Curve: Understanding and properly implementing MVVM can be challenging for developers new to the pattern.

4. Clean Architecture

Domain Layer: Contains the business logic.
Data Layer: Manages data sources and repositories.
Presentation Layer: Handles the UI and presentation logic.
Interface Adapters: Convert data between the different layers.
Pros:

Highly Scalable: Suitable for large, complex applications due to its modular structure.
Testability: Each layer can be tested independently, ensuring thorough and effective testing.
Independent Frameworks: The architecture is not tightly coupled to any framework, making it easier to switch or update technologies.

Cons:

Initial Complexity: Setting up and understanding Clean Architecture can be daunting, especially for smaller teams or projects.
Increased Development Time: The overhead of maintaining strict boundaries between layers can slow down the development process.
Overkill for Simple Apps: May be excessive for small or simple applications due to its detailed and structured nature.

Thanks for reading this far, I'm Voldemort a Software engineer.
I accidentally bumped into a post about a free online internship program, HNG.
There is also provision to be certified and enjoy premium package.

Talking about ReactJs and Nextjs.

walerick — Sun, 30 Jun 2024 18:46:38 +0000

Getting familiar with React

React is an open source and flexible Javascript library that allows developers to develop scalable, simple, and fast frontend interfaces for Single Page Application. It supports a functional programming paradigm and a reactive approach.
It was developed by Facebook.

What is React used for

Social Media Platforms e.g Facebook, Instagram.
Online Video streaming e.g Netflix
SAAS tools e.g Zapier.

Getting familiar with NextJs

Next.Js an open-source and JavaScript framework, allowing you to develop fast and user-friendly web applications and static websites using React.

What is Next.js used for

E-commerce
Landing Pages
Marketing Website

Which should you use for my project?

Selecting a framework or library complete depends on your project needs. React and Next.js are emerging and beneficial tools for your project, but only for performing certain tasks.

Thanks for reading this far. I hope this article helps in a way. There is a an internship program that is currently going on at the moment, HNG11.
This year is their 11th year edition and it's completely free.
However, Applicants have the opportunity tosubscribe for a year premium package.

How I ensured user authentication, by sending emails in Spring Boot

walerick — Sun, 30 Jun 2024 16:56:50 +0000

How to send email in Java Spring Boot

First of all, add the spring-starter-mail dependency.
This can also be added by modifying your project pom.xml file to include the following

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-mail</artifactId>
</dependency>

After you've successfully added the dependency, create a class object and access the the JavaMailSender Interface in your code by following these few steps:

Use the @Autowired annotation, to inject he JavaMailSender interface into the EmailService class.
Create a DemoMailMessage object.
Add email properties by using specific methods (setTo, setSubject, setText).
Call the send() method to send the email message.

Your code should be similar to this:

package com.example;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.mail.SimpleMailMessage;
import org.springframework.mail.javamail.JavaMailSender;
import org.springframework.stereotype.Service;

public class MyClass {
    @Service
public class EmailService {

    @Autowired
    private JavaMailSender mailSender;

    public void sendEmail(String to, String subject, String body) {
        SimpleMailMessage message = new SimpleMailMessage();
        message.setTo(to);
        message.setSubject(subject);
        message.setText(body);

        mailSender.send(message);
    }
}
}

Finally, you need to configure the SMTP server settings in your application.properties file as shown below

spring.mail.host=smtp.example.com
spring.mail.port=25
spring.mail.username=setusername
spring.mail.password=setpassword
spring.mail.properties.mail.smtp.auth=true
spring.mail.properties.mail.smtp.starttls.enable=true

Then you're good to go.

Since you made it this far, There is an internship program, that I stumbled upon twitter where developers can learn more and network better. There is also an option to get Certificate if you subscribe to the premium package instead.