Forem: Monyasau

I Created a new open-source project

Monyasau — Tue, 24 Sep 2024 10:53:14 +0000

I created an opensource file share system available on Linux, Windows, macOS its called polyshare, it works over local network meaning it doesn't need mobile data to work.

PolyShare *: Fast, Cross-Platform Local Network File Sharing
- Technology stack: HTML, CSS, Javascript, NodeJS
- Status: still in development, Beta version available CHANGELOG.

Where to get/download it

Windows,Linux,macOS executables

[https://github.com/monyasau/PolyShare/releases](https://gith...

Repository

[https://github.com/monyasau/PolyShare/](https://github.com/m...

Repository

Feel free to contribute, report issues, or suggest improvements on the Github Repository. Your feedback and contributions are always welcome!

Why i built this

I went through hell trying to transfer stuffs from my windows device to ios and a couple other devices, so i built PolyShare to offer a fast, user-friendly way of sharing large files across devices on the same network without relying on third-party cloud services or external storage. Its speed and simplicity make it ideal for local file sharing in offices, homes, and educational environments.

My Journey into Mobile Development

Monyasau — Fri, 28 Jun 2024 15:37:11 +0000

My HNG Internship Journey in Mobile Development

Mobile development lets me create impactful applications. Joining the HNG Internship, I'm excited to improve my skills.

Mobile Development Platforms

iOS Development:

Pros: High-quality user experience, revenue potential, secure ecosystem.
Cons: Expensive to get into, stringent approval process at Appstore.

Android Development:

Pros: Larger User base, flexibility, lower costs to build for.
Cons: Fragmentation, quality control issues, security concerns.

Software Architecture Patterns

MVC (Model-View-Controller):

Pros: Clear separation of concerns, easy testing, scalabile.
Cons: gets more Complex with growth.

MVVM (Model-View-View-Model):

Pros: Data binding, modularity, enhanced testability.
Cons: Steep learning curve, potential overhead.

Clean Architecture:

Pros: Maintainability, independent layers, flexibility.
Cons: Initial setup, complexity for small projects.

Why HNG Internship?

I believe participating in this program would help improve my skills as I would gain experience and knowledge from colleagues and mentors

Conclusion

Mobile development has immense potential With the HNG Internship, I'm excited about this opportunity.

Visit HNG Internship and HNG Premium to learn more.

This article was written and published by Olanrewaju Olajide

Building an API: Generating Names for Hex Colors

Monyasau — Fri, 28 Jun 2024 14:09:21 +0000

I recently created an API that generates names for hex colors.

Project Concept

The idea behind this project was to create a simple but powerful API that takes a hex color code as input and returns a name associated with that color. This adds a layer of human-readable context to hexadecimal color representation.

Technical Implementation

Step 1: Planning and Design

I started by outlining the API’s functionality and defining the endpoints. The API would accept a hex color code through a GET/POST request and respond with a JSON object containing the color code and its corresponding name.

Step 2: Data Source

I researched existing datasets and libraries, eventually to use a curated list that balanced comprehensiveness and accuracy.

Step 3: Algorithm Design

I developed an algorithm that matches the provided hex color code with the closest color name from the dataset. This involved calculating color similarity based on RGB values and selecting the closest match using a distance metric.

Step 4: API Development

I built it with Express.js, I implemented the API endpoints, ensuring proper validation and error handling. I tested each endpoint locally.

Step 5: Testing

I tested it with different platforms like Postman and insomnia using different hex color inputs to validate accuracy and performance. This included edge cases such as invalid hex codes and boundary conditions.

Use Cases and Applications

The API I developed can be used in a lot of applications, from graphic design tools that suggest color names to educational platforms

Conclusion

Building this API was easy. It taught me valuable lessons in API design, data handling, and so on.

Why HNG Internship?

I plan on gaining knowledge and experience from colleagues and coordinators, refining my skills, and mastering powerful backend features and best practices in the HNG Internship. I’m also very excited to work on real-world projects, collaborate and work with other developers, and deepen my understanding of Backend development.

Visit HNG Internship and HNG Premium.

This article wass written and published by Olanrewaju Olajide

React vs. Svelte: A Quick Comparison of Frontend Technologies

Monyasau — Fri, 28 Jun 2024 12:19:21 +0000

As a web developer, choosing the right frontend framework can significantly impact the efficiency, speed and performance of your projects. While React is pretty popular, Svelte is a close alternative. In this article, I’ll compare Svelte and React, and highlight their key differences and benefits

Svelte, Which is made by Rich Harris, is a new frontend framework that shifts much of the work to compile time which results in highly optimized vanillaJS at runtime, eliminating the need for a virtual DOM unlike React and reducing the bundle size at the end.
React, developed by Facebook, is a popular library for building user interfaces, and applications. It uses a virtual DOM to efficiently update the UI in response to state changes.

Key Differences between Svelte and React:

Virtual DOM Usage: React uses virtual DOM for updating changes in the app while Svelte does not use virtual DOM
JSX Syntax: React uses JSX which is a combination of JavaScript and XML/HTML while Svelte doesn't use JSX

Comparisons of Svelte & React:
1, Performance:

Svelte: Directly updating the DOM lead to faster runtime performance and smaller bundle sizes.
React: Virtual DOM provides efficient UI updates but also results in larger bundle sizes.

2, Learning Curve:

Svelte: Easier to learn with straightforward reactive assignments and simple state management.
React: harder learning curve due to JSX and the virtual DOM concept.

3, Use Cases:

Svelte: when making high-performance applications where bundle size and runtime speed are critical.
React: when making complex applications with extensive state management needs and a robust component structure.

Who wins? : It depends on your project! React for experience and support due to large community, or choose Svelte for speed and ease of use.

My Expectations for HNG Internship with React
I look forward to gaining knowledge and experience from colleagues and coordinators, mastering React powerful features and best practices in the HNG Internship. I’m also very excited to work on real-world projects, collaborate and work with other developers, and deepen my understanding of Frontend development.

For more information about the HNG Internship, visit the HNG Internship homepage and explore HNG Premium services.

This article is written and published by Olanrewaju Olajide