<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Olubiyi Isaac Anu</title>
    <description>The latest articles on DEV Community by Olubiyi Isaac Anu (@kingice97).</description>
    <link>https://dev.to/kingice97</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4244582%2F59a4a310-a32b-4714-b795-03622a436f20.png</url>
      <title>DEV Community: Olubiyi Isaac Anu</title>
      <link>https://dev.to/kingice97</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kingice97"/>
    <language>en</language>
    <item>
      <title>Beyond the Code: The Product Decisions That Shaped King Ice Quiz</title>
      <dc:creator>Olubiyi Isaac Anu</dc:creator>
      <pubDate>Tue, 17 Nov 2026 09:30:30 +0000</pubDate>
      <link>https://dev.to/kingice97/beyond-the-code-the-product-decisions-that-shaped-king-ice-quiz-3126</link>
      <guid>https://dev.to/kingice97/beyond-the-code-the-product-decisions-that-shaped-king-ice-quiz-3126</guid>
      <description>&lt;p&gt;When developers talk about building applications, we often focus on the technologies: React, Node.js, databases, APIs, and everything that makes an application work.&lt;/p&gt;

&lt;p&gt;But there's another side of software development that deserves just as much attention: the decisions behind the product.&lt;/p&gt;

&lt;p&gt;While building King Ice Quiz, I learned that writing code is only one part of creating a useful application. Understanding the people who will use it, the problems they face, and the experience you want to deliver is equally important.&lt;/p&gt;

&lt;p&gt;King Ice Quiz started with an idea: what if online assessments could be more engaging for students while still giving teachers a way to create secure, private assessments?&lt;/p&gt;

&lt;p&gt;That idea influenced how I thought about the product.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Start With the Users, Not the Features&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One of the first things I considered was who would actually use the platform.&lt;/p&gt;

&lt;p&gt;King Ice Quiz wasn't intended for just one type of user.&lt;/p&gt;

&lt;p&gt;There were two important user groups:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Students: People who would participate in quizzes and compete with others in real time.&lt;/li&gt;
&lt;li&gt;Teachers: People who needed a way to create and manage private assessments.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These users had different expectations.&lt;/p&gt;

&lt;p&gt;Students needed an engaging experience, while teachers needed control and privacy when creating assessments.&lt;/p&gt;

&lt;p&gt;This made me think beyond simply building a quiz application. I had to consider how the product could serve both groups without losing sight of their individual needs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Making Learning More Engaging&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Traditional online testing can sometimes feel disconnected.&lt;/p&gt;

&lt;p&gt;I wanted King Ice Quiz to offer something more engaging by introducing real-time competition.&lt;/p&gt;

&lt;p&gt;The idea was to make assessments feel more interactive, giving students an opportunity to participate alongside others rather than simply answering questions in isolation.&lt;/p&gt;

&lt;p&gt;This was one of the reasons real-time functionality became an important part of the product vision.&lt;/p&gt;

&lt;p&gt;For me, technology should not just make an application functional. It should help create a better experience for the people using it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Balancing Engagement With Privacy&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Another important product consideration was the teachers' experience.&lt;/p&gt;

&lt;p&gt;Not every assessment should be public or open to everyone.&lt;/p&gt;

&lt;p&gt;Teachers need the ability to create private assessments, especially when they are preparing tests for specific students or groups.&lt;/p&gt;

&lt;p&gt;This introduced another product requirement: engagement should not come at the expense of privacy and control.&lt;/p&gt;

&lt;p&gt;It was important to think about these needs together rather than treating them as separate concerns.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Thinking Beyond the Initial Idea&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As the project developed, I began to appreciate something important about product development.&lt;/p&gt;

&lt;p&gt;An idea might sound simple at first, but turning it into a working application requires several layers of thinking.&lt;/p&gt;

&lt;p&gt;You have to consider the users, their expectations, the experience, the functionality, and the technical decisions needed to support the product.&lt;/p&gt;

&lt;p&gt;A feature should not exist simply because it is possible to build.&lt;/p&gt;

&lt;p&gt;There should be a reason behind it.&lt;/p&gt;

&lt;p&gt;That mindset has influenced how I approach software development and product decisions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. What Building King Ice Quiz Taught Me&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Building King Ice Quiz has reinforced a few lessons for me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Understand the problem first&lt;/strong&gt;: Before deciding what to build, understand why it needs to exist.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Think about different users&lt;/strong&gt;: One product can serve multiple user groups with different expectations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prioritise the experience&lt;/strong&gt;: Functionality matters, but how people interact with that functionality matters too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Don't confuse features with value&lt;/strong&gt;: Adding more features doesn't automatically make a product better.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Think like a product builder&lt;/strong&gt;: Good engineering should support a clear product purpose.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Final Thoughts&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;King Ice Quiz has been an important learning experience for me, not just from an engineering perspective but also from a product development perspective.&lt;/p&gt;

&lt;p&gt;It has reminded me that building software is about more than making things work.&lt;/p&gt;

&lt;p&gt;It's about understanding people, identifying problems, making thoughtful decisions, and using technology to create something useful.&lt;/p&gt;

&lt;p&gt;I'm still learning, experimenting, and improving as I continue building.&lt;/p&gt;

&lt;p&gt;And that's one of the things I enjoy most about this journey.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The code brings the product to life, but the thinking behind it gives the product direction.&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;King Ice Quiz: &lt;a href="https://king-ice-quiz.vercel.app" rel="noopener noreferrer"&gt;https://king-ice-quiz.vercel.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Portfolio: &lt;a href="https://olubiyi-isaac.vercel.app" rel="noopener noreferrer"&gt;https://olubiyi-isaac.vercel.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Kingice97" rel="noopener noreferrer"&gt;https://github.com/Kingice97&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>showdev</category>
      <category>programming</category>
    </item>
    <item>
      <title>How I Made My Web App and My Name Discoverable by AI Models (SEO &amp; JSON-LD)</title>
      <dc:creator>Olubiyi Isaac Anu</dc:creator>
      <pubDate>Mon, 16 Nov 2026 08:43:14 +0000</pubDate>
      <link>https://dev.to/kingice97/how-i-made-my-web-app-and-my-name-discoverable-by-ai-models-seo-json-ld-h9f</link>
      <guid>https://dev.to/kingice97/how-i-made-my-web-app-and-my-name-discoverable-by-ai-models-seo-json-ld-h9f</guid>
      <description>&lt;p&gt;Have you ever asked ChatGPT, Gemini, or Perplexity a question about a specific developer or a niche web app, and they give you an accurate answer?&lt;/p&gt;

&lt;p&gt;Recently, I wanted to make sure that when people (or AI models) searched for my name, Olubiyi Isaac Anu, they would immediately find my portfolio and my full-stack projects like King Ice Quiz.&lt;/p&gt;

&lt;p&gt;In this article, I’ll break down exactly how I used SEO best practices, JSON-LD structured data, and open-source databases to make my identity and my projects "machine-readable" for AI.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. The Power of JSON-LD Structured Data&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;AI models and search engines don't just read text; they read data. If you want AI to know you are the creator of an app, you have to tell it in a language it understands: Schema.org.&lt;/p&gt;

&lt;p&gt;I added a JSON-LD script to my React app using react-helmet-async. This script explicitly links my name to the application:&lt;/p&gt;

&lt;p&gt;const authorSchema = {&lt;br&gt;
  "&lt;a class="mentioned-user" href="https://dev.to/context"&gt;@context&lt;/a&gt;": "&lt;a href="https://schema.org" rel="noopener noreferrer"&gt;https://schema.org&lt;/a&gt;",&lt;br&gt;
  "@type": "WebApplication",&lt;br&gt;
  "name": "King Ice Quiz",&lt;br&gt;
  "url": "&lt;a href="https://king-ice-quiz.vercel.app" rel="noopener noreferrer"&gt;https://king-ice-quiz.vercel.app&lt;/a&gt;",&lt;br&gt;
  "author": {&lt;br&gt;
    "@type": "Person",&lt;br&gt;
    "name": "Olubiyi Isaac Anu",&lt;br&gt;
    "url": "&lt;a href="https://github.com/Kingice97" rel="noopener noreferrer"&gt;https://github.com/Kingice97&lt;/a&gt;",&lt;br&gt;
    "sameAs": [&lt;br&gt;
      "&lt;a href="https://github.com/Kingice97" rel="noopener noreferrer"&gt;https://github.com/Kingice97&lt;/a&gt;",&lt;br&gt;
      "&lt;a href="https://x.com/IcekidOlubiyi" rel="noopener noreferrer"&gt;https://x.com/IcekidOlubiyi&lt;/a&gt;"&lt;br&gt;
    ]&lt;br&gt;
  }&lt;br&gt;
};&lt;/p&gt;

&lt;p&gt;By doing this, when Google's bots (or AI web crawlers) visit my site, they don't just see a quiz app; they see a structured data point that says: "Olubiyi Isaac Anu is the author of this application."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Creating a Dedicated About Page&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;AI needs a place to verify the claim. I built a dedicated /about page that tells the story of the app, my background as a Software Engineer, and links out to my GitHub and portfolio.&lt;/p&gt;

&lt;p&gt;I ensured that my name is explicitly written in the text and metadata&lt;/p&gt;



&lt;p&gt;&lt;strong&gt;3. Claiming Identity on Wikidata&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Wikidata is the structured database that powers Wikipedia, Google Knowledge Panels, and many AI models. I created a Wikidata item for myself and my project.&lt;/p&gt;

&lt;p&gt;By linking my name to "King Ice Quiz" in Wikidata, I created a digital paper trail that AI can follow. When Wikidata, GitHub, and my website all link to each other, it solidifies the connection.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Indexing and Verification&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Finally, I used Google Search Console to inspect my /about URL. Google validated my structured data (JSON-LD) and confirmed that the page was ready to be indexed. Within days, my name and my app were being recognized correctly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Result&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Now, when you search for "Olubiyi Isaac Anu" or ask an AI web tool who created "King Ice Quiz," the models have all the data they need to give the correct answer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why Every Developer Should Do This&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As developers, we build great things. But if nobody—or no machine—can find them, they don't exist. Implementing basic SEO and structured data is a skill that separates a good developer from a great engineer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Let's Connect&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you are building your own projects and want to make sure they get the recognition they deserve, feel free to connect with me:&lt;/p&gt;

&lt;p&gt;· &lt;strong&gt;Portfolio&lt;/strong&gt;: &lt;a href="https://olubiyi-isaac.vercel.app" rel="noopener noreferrer"&gt;https://olubiyi-isaac.vercel.app&lt;/a&gt;&lt;br&gt;
· &lt;strong&gt;Live App&lt;/strong&gt;: &lt;a href="https://king-ice-quiz.vercel.app" rel="noopener noreferrer"&gt;https://king-ice-quiz.vercel.app&lt;/a&gt;&lt;br&gt;
· &lt;strong&gt;GitHub&lt;/strong&gt;: &lt;a href="https://github.com/Kingice97" rel="noopener noreferrer"&gt;https://github.com/Kingice97&lt;/a&gt;&lt;br&gt;
· &lt;strong&gt;X&lt;/strong&gt;: @IcekidOlubiyi&lt;/p&gt;

&lt;p&gt;If this helped you, let me know in the comments how you handle SEO for your side projects!&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>seo</category>
      <category>javascript</category>
      <category>ai</category>
    </item>
    <item>
      <title>How I Built a Full-Stack Quiz Platform with React, Node.js, and Socket.io</title>
      <dc:creator>Olubiyi Isaac Anu</dc:creator>
      <pubDate>Sat, 14 Nov 2026 14:05:26 +0000</pubDate>
      <link>https://dev.to/kingice97/how-i-built-a-full-stack-quiz-platform-with-react-nodejs-and-socketio-5hjk</link>
      <guid>https://dev.to/kingice97/how-i-built-a-full-stack-quiz-platform-with-react-nodejs-and-socketio-5hjk</guid>
      <description>&lt;p&gt;As a software engineer, I love building tools that solve real problems. I noticed that traditional online testing platforms often feel dull and disconnected. I wanted to build something different—a platform where students could compete in real-time, and teachers could easily create secure, private assessments.&lt;/p&gt;

&lt;p&gt;That’s how King Ice Quiz was born. It is a full-stack web application with a React frontend, a Node.js/Express backend, and real-time chat capabilities powered by Socket.io.&lt;/p&gt;

&lt;p&gt;You can check out the live app here: king-ice-quiz.vercel.app&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Tech Stack&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For this project, I chose a robust MERN-style stack to ensure scalability and real-time performance:&lt;/p&gt;

&lt;p&gt;· Frontend: React.js, React Router, Context API, Socket.io-client&lt;br&gt;
· Backend: Node.js, Express.js, Socket.io&lt;br&gt;
· Database: MongoDB (with Mongoose)&lt;br&gt;
· Authentication: JWT &amp;amp; bcrypt&lt;br&gt;
· Deployment: Vercel (Frontend) &amp;amp; Render (Backend)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. The Core Feature: Private Quiz Codes&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One of the main challenges I wanted to solve was security and privacy for teachers.&lt;/p&gt;

&lt;p&gt;I built a system where teachers (Admins) can create a quiz and generate a unique, 8-character Access Code.&lt;/p&gt;

&lt;p&gt;· If the quiz is marked "Public," it appears on the browse page for everyone.&lt;br&gt;
· If the quiz is "Private," it is completely hidden. Students can only find it by entering the code on the "Join Quiz" page.&lt;/p&gt;

&lt;p&gt;On the backend, I generated unique codes using a mix of alphanumeric characters to prevent collisions, ensuring each quiz has a secure, private entry point.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Real-Time Communication with Socket.io&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I didn't want this to just be a solo experience. I integrated Socket.io to create a real-time chat room.&lt;/p&gt;

&lt;p&gt;Setting up the WebSocket connection on the backend was interesting. I had to manage user connections, track online status, and broadcast messages to specific rooms (like sending a message only to users in a specific quiz room). This transformed the app from a simple test-taker into a social learning environment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Local Scoring &amp;amp; Fallback Logic&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One of the trickiest parts of building a quiz app is handling the score submission. What happens if the user’s internet drops right before they finish?&lt;/p&gt;

&lt;p&gt;I implemented a system where the frontend fetches the quiz with the correct answers hidden, but calculates the score locally as a fallback. If the WebSocket or HTTP request to submit the score to MongoDB fails, the user still sees their result instantly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Security &amp;amp; Role-Based Access&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Since there are different types of users (Students, Teachers/Admins, and Super Admins), I implemented strict Role-Based Access Control (RBAC).&lt;/p&gt;

&lt;p&gt;· Students can only see their own results.&lt;br&gt;
· Teachers can only see the results of students who took their specific quizzes.&lt;br&gt;
· I used bcrypt to hash passwords and JWT (JSON Web Tokens) to secure API routes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. The UI/UX Experience&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I wanted the app to feel like a native mobile app. I implemented a PWA (Progressive Web App) manifest, allowing users to "install" the app on their phones. I also built a custom mobile bottom-navigation bar and supported both Dark and Light modes to make the platform accessible and comfortable for all users.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Lessons Learned&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Building King Ice Quiz taught me a lot about state management, WebSocket connections, and the importance of security in full-stack applications. It was incredibly rewarding to see the transition from a blank folder to a fully deployed, production-ready application.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Let's Connect!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you are a teacher looking for a better way to test your students, or a developer who wants to chat, feel free to reach out!&lt;/p&gt;

&lt;p&gt;· &lt;strong&gt;Live App&lt;/strong&gt;: &lt;a href="https://king-ice-quiz.vercel.app" rel="noopener noreferrer"&gt;https://king-ice-quiz.vercel.app&lt;/a&gt;&lt;br&gt;
· &lt;strong&gt;GitHub&lt;/strong&gt;: &lt;a href="https://github.com/Kingice97" rel="noopener noreferrer"&gt;https://github.com/Kingice97&lt;/a&gt;&lt;br&gt;
· &lt;strong&gt;Twitter (X)&lt;/strong&gt;: @IcekidOlubiyi&lt;/p&gt;

&lt;p&gt;If you found this helpful or have any feedback on the app, let me know in the comments!&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6eey41zspcz9rrf44g4z.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6eey41zspcz9rrf44g4z.jpg" alt=" " width="800" height="411"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>react</category>
      <category>node</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
