Today we shipped frontend v3.1.x and a matching backend release. The headlines: a full sign-in experience polish and faster API responses.
Sign-in experience, polished
Double-fallback OAuth flow
We took the OAuth flow apart and rebuilt the resilience layer:
- Popup mode automatically degrades to redirect mode when blocked
- Signed cookie + origin checks are stricter
- Cross-origin edge cases are now fully covered
The overall sign-in success rate and stability go up noticeably — especially behind corporate networks, with multiple tabs open, or in strict-privacy Safari setups.
In-app browser detection + guidance
Open a Slima link from Instagram, Facebook, Threads, LINE, Twitter/X, or Discord?
In-app browsers usually have spotty Google OAuth support, and sign-in stalls.
The new version:
- Detects when you’re inside an in-app browser
- Shows a friendly prompt: “For the best sign-in experience, we recommend opening this in your system browser”
- Gives you a one-tap button to switch to Safari / Chrome
For visitors arriving from social apps, sign-in is seamless.
API performance upgrade
Books API returns the full library in one call
GET /api/v1/books now defaults to per_page=100, up from the previous smaller value.
Who feels this most:
- Slima MCP users — Claude Code, Cursor, and other MCP clients pull your entire library in one call, no pagination loop required
- Automation scripts — batch tools (e.g. backing up all manuscripts) run noticeably faster
- Front-end Book List — loads quicker, especially for power users with 50+ books
Also in this release
- OAuth signed cookie origin handling is stricter — consistent behavior across multiple-tab sign-in
- Integration test coverage expanded — sign-in paths now have full RED → GREEN test protection
- i18n completeness — all 5 locales filled in for Script Studio Import
Coming up
Continued editor polish, more Script Studio import sources, and we’re starting to think about the next studio.