Roadmap

Devmaniac roadmap

Devmaniac is being built to help developers document live projects, showcase finished work, and turn real progress into proof of work.

The roadmap is focused on making Devmaniac more useful for builders, not adding random features just because they sound impressive. The priority is simple: help developers show what they are building, what they are learning, and how they are improving over time.

Current version

Devmaniac is currently in an early MVP stage.

The MVP focuses on the core workflow:

• Create a developer profile
• Add live projects
• Post project journals
• Show finished projects
• Collect stars and bookmarks
• Send feedback and support requests
• Build public proof of work through real activity

The MVP is intentionally focused. A small product with a clear purpose is better than a bloated product that tries to be everything and becomes a confused monster. 🧡

Roadmap principles

Devmaniac roadmap decisions are guided by a few principles.

• Live projects first: Devmaniac should prioritize active building, not only finished portfolios.
• Proof over claims: Project activity should prove skills better than empty tech stack lists.
• Clarity over noise: Features should make work easier to understand, not harder.
• Honest building: Bugs, blockers, pauses, and unfinished work should be possible to document clearly.
• Useful feedback: User feedback should shape the platform.
• Simple workflow: Developers should be able to post progress without fighting the product.

Recently shipped

These are the early foundation pieces already part of Devmaniac or the current MVP direction.

• Developer profiles
• Profile onboarding
• Live project creation
• Finished project showcase
• Project journals
• Stars and bookmarks
• Feedback and support flows
• Public documentation site
• Basic admin tools for managing platform activity

Near-term improvements

These improvements are focused on making the current MVP smoother and clearer.

Better onboarding

Onboarding should help new users understand what Devmaniac is, what to do first, and why live projects matter.

Planned improvements include:

• Clearer signup-to-profile flow
• Better onboarding guide screens
• Cleaner explanations for live projects and finished projects
• Better handling for sync errors
• More helpful empty states after signup

Better live project creation

Live projects are the center of Devmaniac, so the create flow should feel simple and obvious.

Planned improvements include:

• Clearer live project form
• Better status options
• Improved tech stack input
• Better image upload experience
• Clearer difference between live and finished projects

Better journals

Journals should make progress easy to write and easy to read.

Planned improvements include:

• Cleaner journal editor
• Better journal timeline UI
• Journal image support improvements
• Code snippet support
• Journal reactions and replies
• Better journal type labels

Version 1 direction

Version 1 should make Devmaniac feel less like a basic MVP and more like a serious build-in-public platform for developers.

The focus is not random GitHub importing or inflated profile scores. The focus is controlled, meaningful project activity.

Manual-first GitHub integration

GitHub integration should be careful. Auto-importing every repository can create a bad experience because many developers have old, messy, test, or abandoned repositories.

Instead of importing everything automatically, Devmaniac should let users choose what matters.

Planned GitHub improvements may include:

• Connect GitHub account
• Select specific repositories to attach
• Import selected repository metadata
• Show latest commits for selected live projects
• Connect commits to project journals when useful
• Avoid rating users based on random repository count

This keeps Devmaniac focused on meaningful proof of work, not noisy repo flexing.

CLI for live project updates

A Devmaniac CLI could make progress logging faster for developers who live in the terminal.

Possible CLI features:

• Create a journal from the terminal
• Attach a journal to a live project
• Log progress without opening the browser
• Connect local project folders to Devmaniac projects
• Post deployment notes quickly
• Save draft updates before publishing

This is especially useful because Devmaniac is about tracking what developers are actively learning and building.

Better project discovery

Devmaniac should make it easier to discover interesting builders and live projects.

Planned discovery improvements may include:

• Explore page improvements
• Project categories
• Search by tech stack
• Search by project status
• Featured live projects
• Trending project journals
• Better filtering for students, self-taught developers, hackathon builders, and open-source builders

Better profile proof

Profiles should show real activity, not fake numbers.

Planned profile improvements may include:

• Better profile stats
• More useful project activity summaries
• Current build improvements
• Visible live project momentum
• Clearer finished project sections
• Better social and GitHub link presentation

Future ideas

These ideas are possible future directions, but they should only be added if they support the core mission.

Notifications

Notifications could help users follow project activity and stay connected to feedback.

Possible notification types:

• Someone starred your project
• Someone bookmarked your project
• Someone commented on a journal
• A followed builder posted a new update
• A bookmarked live project posted a new journal

Comments and discussion

Comments can help builders receive feedback directly on projects and journals.

The challenge is keeping comments useful. Devmaniac should avoid becoming noisy. Comments should support feedback, questions, and builder-to-builder learning.

Mobile experience

A better mobile experience would help developers post quick updates, screenshots, bug notes, and progress journals from anywhere.

Possible mobile improvements:

• Better responsive UI
• Faster project updates from phone
• Mobile-first journal posting
• Image upload improvements
• Possible React Native app later

Public changelog

A public changelog can show how Devmaniac itself is improving over time.

This matches the product philosophy. If Devmaniac tells developers to document progress, Devmaniac should document its own progress too.

Status page

A status page can help users understand platform incidents, uptime, maintenance, and known issues.

This may become useful as more users depend on Devmaniac.

What is not the priority?

Some features sound attractive but can hurt the product if added too early.

Not the current priority:

• Auto-importing every GitHub repository by default
• Fake profile ratings based on inflated repository count
• Adding social features before the core project workflow is strong
• Turning Devmaniac into a generic social network
• Adding AI features without clear user value
• Overcomplicating onboarding before users understand the basics

The product should stay focused. Devmaniac wins by helping builders show real work clearly.

How users can shape the roadmap

Devmaniac is built from real builder feedback.

Users can help shape the roadmap by reporting:

• What felt confusing during onboarding
• What made them more likely to post a live project
• What stopped them from posting updates
• What project fields felt unnecessary
• What features would make them return
• What bugs blocked normal usage
• What proof of work they want to show better

The best roadmap is not built from founder ego. It is built from user behavior, product vision, and painful honesty.

The core direction

Devmaniac roadmap should answer:

What should we build next to help developers document real progress and turn active projects into proof of work?

If a feature supports that mission, it belongs in the conversation. If it does not, it can wait.