Sortinder

Sortinder is a self-reported Windows desktop application designed to organize cluttered folders through a swipe-through workflow. The author describes it as a tool that allows users to review files one-by-one, make decisions (keep, skip, trash), and benefit from duplicate detection and file-type guidance. It was built by one person (Aleksei Krasnov) using Tauri, Rust, TypeScript, GitLab, and GPT-5.6 as part of a hackathon submission.

The project is presented as a utility for personal file management, with an emphasis on safety, reversibility, and ease-of-use. It includes features like local trash folder support, undo functionality, duplicate detection by size and hash, and recursive folder scanning.

Key commercial due-diligence question: What is the actual demand for such a tool, and how does it differ from existing file management solutions?

The description contains no evidence of revenue, customers, or adoption. It is entirely self-reported and unverified.

• The description states that Sortinder is a Windows desktop app.
• It is built using Tauri (web-based frontend + Rust backend).
• It supports both portable executable and Windows installer formats.
• It enables users to review files one-by-one via swipe-through flow.
• Users can choose to keep, skip, or trash items.
• Trashed items are stored in a local reversible trash folder.
• The app provides file-type-aware guidance and detects duplicates using file size and SHA-256 hash comparison.
• Actions are validated by the backend to remain within user-selected folders.
• Undo support is included for actions.

Inference: Based on the author's description, this appears to be a lightweight desktop utility aimed at simplifying personal file organization tasks. It is not described as a commercial product or service with monetization mechanisms.

• The description states that Sortinder aims to make cleaning cluttered folders feel "lighter and more deliberate."
• It positions itself as an alternative to switching between file lists, previews, and opening items individually.
• The app is described as a tool for reviewing one item at a time with quick decisions.
• It emphasizes safety through reversible actions, undo support, and backend validation.
• The author mentions using GPT-5.6 in development, suggesting AI-assisted creation but not implying AI-powered functionality during use.

Inference: The positioning appears to be that of a simple, safe, and user-friendly file organizer for individuals managing large or disorganized directories. It does not claim to be part of a larger ecosystem or platform.

• The description does not name specific customer segments.
• It implies the target is someone who manages cluttered folders on Windows.
• The app is described as useful for "cleaning up" Downloads folders and similar disorganized directories.
• No explicit mention of professional users, teams, or enterprise adoption.

Inference: Based on the author's framing, the ICP likely includes individual Windows users with disorganized file collections who want a safer, more streamlined way to sort files. There is no evidence of targeting businesses or specific industries.

• The description does not mention any pricing model.
• No indication of monetization strategy or revenue streams.
• It is described as a desktop app built for personal use.
• No subscription, licensing, or transactional fees are referenced.

Inference: There is no evidence of a business model beyond the author's own development effort. The project seems to be a prototype or hobbyist tool without commercial intent.

• Built with Tauri (cross-platform desktop framework).
• Uses Rust for backend logic.
• Frontend is web-based (TypeScript).
• Supports both portable and installer versions.
• Includes safety features like path validation, local trash folder, undo support.
• Duplicate detection uses file size and SHA-256 hash comparison.
• Designed to handle nested folders recursively.
• Demo mode avoids touching real user files.

Inference: The technical stack suggests a modern, cross-platform approach with attention to user experience and safety. However, no evidence of scalability or production-grade infrastructure is provided.

• The project was submitted to the OpenAI 2026 hackathon.
• It is described as a small project built by one developer (Aleksei Krasnov).
• No mention of users, downloads, or adoption metrics.
• No evidence of revenue, customer feedback, or usage data.

Inference: There is no traction or maturity signal beyond the initial development and submission to a hackathon. The tool has not been released for public consumption or tested in real-world conditions.

• The description does not reference competitors.
• No mention of existing tools for file organization or sorting on Windows.
• It is implied that current solutions are frustrating or inefficient, but no specific alternatives are named.

Inference: Without evidence of competitive analysis or market positioning, it's unclear how Sortinder fits into the broader landscape of file management utilities. The author does not claim to be solving a known gap in the market.

• The project is self-reported and unverified; no third-party validation.
• No evidence of revenue, customers, or adoption.
• The app is described as a "small project" built by one person.
• It was submitted to a hackathon — suggesting it may be experimental or incomplete.
• No mention of long-term maintenance plans or roadmap beyond basic improvements.
• Uses GPT-5.6 in development but does not imply AI functionality during use.

Inference: The lack of traction, commercial viability, and evidence of real-world usage raises questions about whether this tool will evolve into a product with market demand.

1. What specific problem are you trying to solve, and how do you know users face that issue?
2. Have you tested Sortinder with actual users or in real-world scenarios beyond the hackathon?
3. How does Sortinder compare to existing file management tools on Windows?
4. Is there any plan for monetization or commercialization beyond personal use?
5. What are your plans for ongoing development, support, and updates?
6. How do you intend to scale beyond a single developer’s effort?