You are browsing as a guest. Sign up (or log in) to start making projects!

Cret

@Cret

Joined June 1st, 2026

  • 25Devlogs
  • 7Projects
  • 3Ships
  • 47Votes
Open comments for this post

9h 49m 20s logged

This project is designed specifically for individuals with ADHD. Research indicates that the ADHD population faces physiologically unique and severe cognitive challenges:

First, their working memory bandwidth—responsible for holding fleeting thoughts—is extremely narrow and exceptionally prone to collapse. While a neurotypical brain typically retains working memory for 10 to 15 seconds, an ADHD brain often loses it in just a few seconds. Abnormalities in prefrontal dopamine pathways render their attention extraordinarily fragile. Any minor external stimulus—such as unlocking a screen, a 0.5-second app cold-start delay, or cumbersome “New Note” buttons and categorization workflows—acts like a disruptive sensory intrusion. It instantly shatters and dissolves newly formed neural circuits, causing brilliant sparks of inspiration to vanish forever. What is most devastating is knowing they just had a brilliant idea, yet it has been permanently erased. This “acute thought evaporation” frequently triggers deep self-blame and mental exhaustion.

Second, they struggle with severe executive dysfunction and “initiation paralysis.” The vast majority of productivity and note-taking apps on the market are built around neurotypical prefrontal logic, forcing users through preliminary steps like titling, choosing folders, manual tagging, and formatting before they can even begin recording. While simple to neurotypicals, these prerequisites are instantly amplified in the ADHD brain into an overwhelming, suffocating decision-making load, inevitably leading to executive overload and abandonment of the task.

Furthermore, individuals with ADHD suffer profoundly from “Object Permanence Failure” and “Retrieval Cue Failure.” Under the premise of “out of sight, out of mind,” content buried within nested folders quickly turns into a permanently forgotten “digital graveyard.” Conversely, keeping everything on the home screen triggers intense visual overload and avoidance anxiety. When attempting retrieval, they often struggle to recall exact keywords, rendering traditional keyword-dependent search completely useless.

This is precisely why Fleeting abandons the conventional, counterproductive trap of feature bloat. Instead, it embraces neurodiversity through radical, physics-level reduction. By compressing the entire process into a single, intuitive “Launch-to-Record” action and silently attaching implicit spatio-temporal fingerprints (such as time and context) in the background, Fleeting shifts the burden from “active keyword recall” to “contextual reconstruction and visual recognition.” It serves as a secure, guilt-free external thought airbag for these fragile yet precious sparks of insight.

0
0
12
Ship ✨ Blessed

Thank you to visit here. I am the frontend developer

You can create a new account or use our demo account
demo account: pawntest2026
password: test123456789abc

  • 2 devlogs
  • 20h
  • 5.89x multiplier
  • 74 Stardust
Try project → See source code →
Open comments for this post

19h 8m 17s logged

InspireFlow

An AI-powered creative workflow assistant for creators.

InspireFlow (升变) is a project built by a team of high school students during AdventureX 2026. It explores how AI can help creators manage the journey from an initial idea to a finished piece of content, while keeping their creative assets organized and under their control.

What are we building?

Creating content often involves scattered ideas, unfinished drafts, collaboration messages, brand requirements, and production plans across different tools.

InspireFlow aims to provide a unified workflow where creators can:

  • Capture and organize creative ideas
  • Transform rough thoughts into structured content plans
  • Assist with outlines, scripts, and production workflows using AI
  • Keep track of creative assets and collaboration history
  • Create verifiable records for important creative materials

The goal is to make the creative process more organized, transparent, and easier to manage.

Why InspireFlow?

Many creators spend significant time developing ideas, writing drafts, and communicating with collaborators. However, these valuable creative assets are often stored across disconnected platforms, making it difficult to track ownership, changes, and the evolution of an idea.

InspireFlow explores a different approach: creators should have better visibility and control over the creative process behind their work.

How it works

InspireFlow combines several technologies:

  • AI assistance — helping creators structure ideas and improve workflows
  • On-device processing — designed to keep sensitive creative information local whenever possible
  • iOS application — providing a native experience for creators
  • Hardware interaction — integrating with devices such as smart rings for easier idea capture
  • Blockchain-based records — exploring ways to create verifiable records for creative assets

Current Status

InspireFlow is currently a prototype/demo developed during AdventureX 2026.

The project was built within a short hackathon timeframe, including:

  • A complete iOS demo application
  • AI-assisted creative workflows
  • Hardware integration experiments
  • A prototype for creative asset verification

There is still a lot to improve, and we are continuing to explore how AI can better support creators.

Vision

From the first spark of an idea to the final delivery, creators should have a clearer and more connected workflow.

InspireFlow is an experiment toward building tools that help creators focus on creativity while maintaining better control over their creative process.

0
0
8
Open comments for this post

4h 53m 40s logged

I’ve been working on the AppleMusic-Downloader project, primarily debugging a Windows-specific issue where the desktop app would hang during downloads. The root cause turned out to be PyInstaller’s --windowed mode setting sys.stdout and sys.stderr to None, which broke async libraries like httpx and asyncio. The fix was calling AllocConsole() on Windows to allocate a visible console window and properly redirect all three standard streams (stdin, stdout, stderr). I also cleaned up unnecessary debug code (log file output, /api/logs endpoint), added step-by-step logging in the download pipeline to help diagnose future issues, fixed a few i18n key mismatches in the frontend, and added a note in both READMEs telling Windows users not to close the console window.

0
0
18
Ship ✨ Blessed

The initial phase of this project involved some debugging work.
A few days ago, I officially began the refactoring of this project. I removed redundant code and modules, abandoned the cumbersome PyQt, built a standard API backend using FastAPI, and built the web frontend using Next.js.

You can run the packaged software now to try it out (don’t forget to install ffmpeg). If you don’t have an Apple Music subscription, DM @Cret on Slack and I’ll provide you with my own cookies.txt file.

  • 17 devlogs
  • 25h
  • 9.89x multiplier
  • 298 Stardust
Try project → See source code →
Open comments for this post

2h 2m logged

Remove Windows-specific GUI components and associated files from the project, including CMake configurations, resource files, and source code for the Flutter window implementation. This cleanup streamlines the project structure and eliminates unnecessary dependencies for non-Windows platforms.

0
0
5
Open comments for this post

1h 12m 13s logged

I ultimately gave up on using Flutter for frontend development; it was simply too difficult. Instead, I am using Next.js combined with pywebview to build the desktop frontend.

0
0
4
Open comments for this post

1h 39m 36s logged

I have completed the API construction; in this phase, I encapsulated all of gamdl’s parameters—aligning them with the definitions in core_downloader.py—into a unified API. Next up is learning Flutter for the frontend.

0
0
4
Loading more…

Followers

Loading…