A personal interface for your tools
Your software. Your interface.
You should not have to learn a new way to work every time you open an app. Roscelin is being built to bring your tools into an interface shaped around you.
In developmentThe preview below uses sample data.
Same task. A different way to work.
Explore how one workspace could adapt to different preferences without changing the underlying task.
Interactive concept · sample data · no live connections
Focused
Now
Confirm event dates with the venue
Reply to the venue and confirm 18 April.
The venue offered 18 or 25 April and is waiting for an answer.
Up next Proofread the final draft, which waits on this task.
Detailed
| Task | Status | Priority | Owner | Due | Updated |
|---|---|---|---|---|---|
| #41 Draft the welcome note | Done | Normal | Ana | Mon 6 Apr | Yesterday |
| #42 Confirm event dates with the venueCurrent | In progress | High | You | Thu 9 Apr | 09:12 |
| #43 Choose the cover photo | Open | Normal | Sam | Fri 10 Apr | Mon |
| #44 Proofread the final draft | Open | Normal | You | Tue 14 Apr | Mon |
| #45 Send to the print shop | Open | Low | Ana | Thu 16 Apr | Last week |
No tasks match this filter.
Selected: #42 Confirm event dates with the venue · 5 comments · Label: Events
Delete is unavailable: this sample integration doesn’t offer it. Use Sample Tasks itself.
Guided
Step 1 of 3
Check the task
You’re confirming the event dates with the venue. It’s due Thu 9 Apr. The venue offered 18 or 25 April.
Step 2 of 3
Has the venue confirmed 18 April?
Choose one. Nothing changes until you review it.
Step 3 of 3
Review the change
You’ll see exactly what would change, and where, before anything happens.
Review change
- App
- Sample Tasks (simulated)
- Item
- #42 Confirm event dates with the venue
- Change
- Status: In progresstoDone
- Unchanged
- Title, priority, owner, due date, notes
In the product, this would go through the app’s own supported update action. The result would then be checked by reading the task again before being reported.
Preview only. No application was changed.
These views are predefined for this page; nothing here is generated live. In production, Roscelin is intended to compose surfaces like these from an app’s supported capabilities and your preferences.
Change the interface, not the way you think.
Make room for what matters.
Choose the detail, density and controls that fit the task in front of you.
In the prototype: three fixed layouts, plus density, text size and contrast settings.
Planned: layouts generated for the task.
Keep your preferences with you.
Roscelin’s direction is a consistent personal interaction profile across supported tools, rather than a fresh start in every app.
In the prototype: a local profile, used with one tested app.
Direction: the same profile across supported tools.
Stay in control.
The original application remains accessible. Changes should be visible, grounded in real capabilities and checked against the intended result.
In the prototype: review before applying, a check by reading the app again, and a link back to the original app.
A new surface. A clear connection to your tools.
How it works in detailIntegration
Understand the available tools.
Read the capabilities and relevant state an authorized integration can actually expose.
Planning + trusted components
Shape the interface.
Compose a useful task surface from trusted components and your explicit preferences.
Application execution
Act and verify.
Route an authorized action to the original app and check the resulting state.
Your surface
What you see, approve and can undo. Each item shows where it came from.
a layout built from trusted components
only the action you approved
Planning
Proposes a layout using only trusted components and actions the integration supports. It cannot invent an action or run code of its own.
Today fixed, deterministic layouts
Planned model-assisted proposals
Trusted controls and checks
Sends the approved action through the app’s supported route, then reads the app again. A result it cannot confirm is reported as unknown, not as done.
capabilities and current state
supported action read back
Original app
The source of truth. It stays as it is and stays available to you.
Browser extension first. Desktop integration requires a separate companion and tested app support. Universal compatibility is a direction, not a launch promise.
Adaptive should not mean unpredictable.
What each principle means in practiceStable when you need it.
Your accepted workspace should not rearrange itself while you are using it.
Clear about its limits.
Unsupported actions should stay unsupported, not become optimistic guesses.
Designed for different people.
Simple, expert, keyboard-first and accessible interactions belong in the same product.
Honest about outcomes.
An attempted action is not the same as a verified result.
A big direction. A deliberate starting point.
Roscelin is in development. A browser-first prototype has been tested with a real Vikunja integration. Generated layouts, broader app support and a Windows companion are next steps, not features available today.
Last updated
- Prototype
Browser-first work with a real Vikunja integration and reported action-verification tests.
- Planned
AI-generated layouts and additional tested adapters.
- Planned expansion
Windows companion and cross-app workspaces.
Engineering detail: a same-field race test exercises what happens when a target field changes before an action completes. With the tested app it reproduces a real gap, which is documented rather than hidden.Full project status