How to Report Bugs and Feature Requests for MikesBlogDesign Vibe Coding Projects

Hey friends! I’ve been diving deep into vibe coding lately, churning out a ton of software, applications, and projects under the MikesBlogDesign vibe. I absolutely love it when you try them out and send me your thoughts—whether it’s spotting a bug or suggesting a killer new feature. Your feedback is gold! However, to make sure I can act on it efficiently, I need it to be clear and structured. That’s why I’ve put together this Standard Operating Procedure (SOP) for reporting bugs and feature requests. Follow these steps, and we’ll keep the vibes high and the code flowing smoothly.

If you’re reporting something, please send it to me via email at feedback@mikesblogdesign.com or through our designated feedback channel. Include as much detail as possible to help me reproduce and resolve issues quickly.

Reporting a Bug

Found a bug? Awesome—don’t let it slip away! Gather the following information to make your report super helpful. I’ve expanded on the basics to cover everything I might need.

  1. Describe the Issue
    • What were you trying to do?
    • What did you expect to happen?
    • What actually happened? Be as specific as possible (e.g., “The button turned blue instead of red, and nothing loaded”).
  2. Steps to Reproduce
    • List the exact steps you took leading up to the bug. Number them for clarity (e.g., 1. Open the app, 2. Click on ‘Settings’, 3. Toggle the dark mode switch).
    • This helps me recreate the problem in my environment.
  3. Capture Visual Evidence
    • Take a screenshot of the bug in action. If it’s on a mobile device, a photo from your phone works too!
    • For dynamic issues (like crashes or animations), consider a short screen recording or video.
    • Tools: Use built-in screenshot tools (e.g., Snipping Tool on Windows, Command+Shift+4 on Mac) or apps like Loom for videos.
  4. Check the Developer Console
    • This might sound intimidating if you’re not a dev, but it’s straightforward and provides crucial error details.
    • Follow our dedicated guide here: How to Access and Copy from the Dev Console.
    • Copy any error messages (usually in red) and include them in your report.
  5. Provide Environment Details
    • What device are you using? (e.g., iPhone 14, Windows PC)
    • Operating System and version (e.g., iOS 17, Windows 11)
    • Browser and version if applicable (e.g., Chrome 115, Safari 16)
    • Version of the app or project you’re testing (if known).
    • Any other relevant info, like network conditions or extensions/plugins.
  6. Additional Notes
    • Has this happened before? Is it consistent or intermittent?
    • Any workarounds you’ve found?

Submitting a Feature Request

Got an idea to make the project even better? I love hearing about new features! Here’s how to submit one effectively so I can evaluate and prioritize it.

  1. Describe the Feature
    • What is the feature? Be clear and concise (e.g., “Add a dark mode toggle”).
  2. Explain the Use Case
    • Why do you want this? How would it improve your experience?
    • Example: “Dark mode would make the app easier on the eyes during late-night use.”
  3. Provide Details or Ideas
    • Any suggestions on how it could work? (e.g., “A switch in the settings menu”)
    • Include sketches, mockups, or references to similar features in other apps if you have them.
    • Screenshots or photos of your ideas are welcome!
  4. Priority and Impact
    • How important is this to you? (e.g., “Nice-to-have” vs. “Must-have”)
    • Who else might benefit? (e.g., “Useful for mobile users”)

Pro Tip: The more details you provide, the faster I can address bugs or consider features. Your input keeps the vibe coding alive—thanks for being part of it!

By following this SOP, you’re helping me maintain high-quality projects and iterate quickly. If you have questions about this process, hit me up!

Need more help? Contact us at support@mikesblogdesign.com.