OpenAI 2026 hackathon

NibGlide

Trackpad-like direct scrolling and browser gestures for macOS pen displays.

Solo project by まぐねた / mag_neta · 1 likes · 0 comments

Archive position — measured, not model output

1 like on Devpost

506 of the 7,856 archived projects have more likes, and 1,758 share exactly 1 — so this project's #1,531 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

NibGlide is a macOS application designed to enable direct scrolling and browser gestures using a pen on pen displays, without disrupting native drawing behavior. The author describes it as an input utility that transforms only tablet-marked pen contact into scroll actions, with momentum and gesture recognition tailored for creative workflows.

The project is self-reported as a Swift-based macOS app built with AppKit and system frameworks like CoreGraphics and ScreenCaptureKit. It uses AI tools (Codex + GPT-5.6) in development, including architecture design, testing, and debugging.

Key commercial due-diligence questions:

  1. Is there any evidence of user adoption or feedback beyond the author’s own use?
  2. What is the actual scope of compatibility with different pen displays and drivers?
  3. How does this product differ from existing solutions (e.g., Karabiner-Elements)?
  4. Are there any commercial plans or monetization strategies?

The single most important open question: What traction, if any, exists beyond the author’s personal development and testing?

Back to contents

What The Product Actually Is

The description states that NibGlide is a macOS application that runs in the menu bar and transforms only tablet-marked pen contact into scrolling or browser gestures.

  • It supports direct pen movement for scrolling content under the cursor.
  • Release velocity produces controlled exponential momentum.
  • Automatic mode handles when users mean to draw, click, select text, or scroll.
  • It includes visual feedback during hold periods (white-and-gray arc).
  • Browser-specific behavior allows only identified elements to become native drags.
  • A dedicated scroll contact can be created via a configurable key.
  • Horizontal gestures in browsers trigger Back/Forward navigation with edge-clipped affordance.
  • The app has a fail-open recovery system ensuring no input-engine faults trap the mouse, keyboard, or trackpad.

Inferred: The product is a lightweight utility that operates at the system level through macOS event taps and integrates with accessibility APIs to distinguish between drawing and scrolling actions.

Back to contents

Positioning & Claim Evolution

The author positions NibGlide as an extension of pen display usability — aiming for "quiet" and "predictable" interaction. It claims to make scrolling feel like a natural continuation of the pen, avoiding disruption during creative workflows.

Claims:

  • Scrolling feels like a quiet extension of the pen.
  • Direct while touching, physical after release.
  • Predictable in browsers.
  • Completely absent when user is drawing.

Inferred: The positioning reflects a niche market need for better pen-to-scroll mapping on macOS, especially for artists using pen displays. It does not claim to be a general-purpose input remapping tool but rather a specialized utility for creative professionals.

Back to contents

Target Customer & ICP

The description implies the target customer is creative professionals who use pen displays (e.g., digital artists, illustrators) on macOS. These users are likely already familiar with drawing tools like Clip Studio Paint and may be frustrated by current navigation limitations.

  • The app is designed to work within creative applications without interfering with native drawing behavior.
  • It targets users who value precision and minimal disruption in their workflow.
  • A key use case involves avoiding accidental brush selection in dense palettes.

Inferred: The ICP likely includes individuals or small teams using pen displays for design, illustration, or animation — not enterprise customers or general consumers.

Back to contents

Business Model & Pricing Evidence

Not evidenced. There is no mention of pricing, licensing, monetization strategy, or any commercial model beyond the author’s own development and testing.

Back to contents

Technical & Delivery Signals

The project is described as a Swift 6 macOS 15+ application using AppKit and public system frameworks such as CoreGraphics, ScreenCaptureKit, and ServiceManagement. It uses Accessibility APIs for arbitration between actions.

Key technical elements:

  • Input boundary provided by CoreGraphics event taps.
  • Dedicated serial input thread owns gesture and recovery state.
  • Pure core module contains scroll state machine, velocity estimator, momentum integrator, browser-history recognizer, interaction policy, settings migration, and fail-open recovery policy.
  • AppKit handles menu-bar experience, onboarding, settings, browser overlay, and optional Evidence Sessions.
  • Codex + GPT-5.6 were used for research, architecture, implementation, testing, and evidence analysis.

Inferred: The app is built with performance in mind, minimizing latency and avoiding interference with other input methods. It appears to be a low-level system utility aimed at optimizing pen interaction on macOS.

Back to contents

Traction & Maturity Signals

Not evidenced. No data about users, adoption, or product maturity beyond the author’s own development experience is provided.

Back to contents

Competitive Context

Not evidenced. The description does not compare NibGlide to existing tools like Karabiner-Elements or other gesture-based utilities for macOS.

Inferred: Given its focus on pen-specific scrolling and browser gestures, it may compete with general input remapping tools or specialized drawing utilities, but no such comparisons are made.

Back to contents

Key Risks & Red Flags

  1. No traction evidence: No users, customers, or adoption data provided.
  2. Limited scope: Only tested on specific hardware (Huion) and software environments.
  3. Unproven commercial viability: No indication of monetization or business model.
  4. AI dependency: Heavy reliance on AI tools for development raises questions about long-term maintainability or scalability without those tools.
  5. Single-person team: One developer implies limited capacity for iteration, support, or growth.

Back to contents

Diligence Questions To Ask The Founders

  1. What real-world feedback have you received from users beyond your own testing?
  2. How many pen-display vendors and driver versions have been validated?
  3. Are there any plans to expand beyond the current Huion-focused boundary?
  4. What are the key differences between NibGlide and existing tools like Karabiner-Elements?
  5. Is there a plan for monetization or commercial use of this tool?
  6. How do you intend to ensure ongoing compatibility with future macOS versions?

Back to contents

Investment/Partnership Verdict

Not evidenced. No information is available regarding funding, valuation, or any investment or partnership interest in the project.

The author describes NibGlide as a personal hackathon project built using Swift and AI tools. It is not demonstrated to have traction, revenue, or a clear path to market beyond its own development. Without evidence of user adoption, commercial viability, or strategic positioning, there is insufficient basis for an investment or partnership conclusion.

The product shows technical sophistication but lacks any indication of broader impact or scalability. The single-person team and lack of external validation raise concerns about long-term sustainability and growth potential.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.