Two products for scheduling software: UI components for JavaScript, React, Angular, Vue and jQuery, and Connect, a calendar API for Google, Outlook, Apple and CalDAV. Used together or on their own.
Mobiscroll started as a date and time picker that worked properly on a phone, back when almost nothing did. Teams kept asking for the thing around the picker — the scheduler, the calendar, the resource timeline — so that is what it became.
The approach has not changed: a toolset, not an opinionated system. Native components per framework, not wrappers around one implementation. Support is answered by the developers who wrote the code.
Two products now. Mobiscroll UI is the scheduling interface. Connect is the calendar layer — OAuth, normalized data, sync across providers — and it works just as well under another frontend.
Our stack
Two products, one idea: give teams the pieces, not a finished opinion.
Mobiscroll UI ships as native builds for JavaScript, jQuery, Angular, React and Vue — one core, five real integrations, not a wrapper around a single implementation. TypeScript types, ESM and CommonJS. 400+ demos, all runnable with source.
Mobiscroll Connect is a REST API with OAuth 2.0, webhooks and calendar sync across Google Calendar, Outlook, Apple Calendar and CalDAV. SDKs for Node.js, Python, PHP, .NET, Java, Go and Ruby. No Mobiscroll UI required.
0 posts published
1 member
loading...
We're a place where coders share, stay up-to-date and grow their careers.
