What EPUB Features Are Not Included in the Standard epuBear SDK?

The standard epuBear SDK ships with a defined feature set that becomes available immediately upon purchase, but several capabilities fall outside that scope and require custom development. Based on the vendor's own description, full or particular EPUB 3 support, DRM integration, and other custom features are not part of the standard package — they are delivered by the epuBear development team as custom solutions with ongoing support. If your product roadmap depends on any of these, plan for a custom engagement rather than assuming the base SDK covers them.

What the standard SDK does include

To judge what's missing, it helps to know what you get out of the box. According to the product page, the following are available immediately upon purchase:

• EPUB 2 and EPUB 3 compatibility
• Reading EPUB files from file storage or loaded into memory
• Extracting EPUB document information
• Rendering pages to bitmap images
• Multiple languages, including vertical and right-to-left writing
• Navigation features
• Customizable reading experience
• Bookmark management
• Text search
• Text selection (highlight and underline)
• Text notes
• Text-to-Speech support
• Audio and video playback within EPUB content
• Opening and zooming pictures within EPUB content

The SDK is described as a closed-source cross-platform core with wrappers for Kotlin (Android), Swift (iOS), C# (MAUI), and Dart (Flutter).

Features that require custom work

Full or particular EPUB 3 support

The page lists "EPUB 2 and EPUB 3 compatibility" as a standard feature, yet also names "full or particular EPUB 3 support" as an example of additional functionality requiring custom delivery. The practical reading: baseline EPUB 3 compatibility is included, but if your content relies on specific EPUB 3 capabilities beyond that baseline, treat it as a customization request and confirm coverage with the vendor before committing.

DRM integration

DRM integration is explicitly listed as a custom feature, not a standard one. If you distribute protected content — for example, a subscription reading app that must honor a publisher's rights-management scheme — you cannot assume the base SDK handles it. This is a scoping and licensing conversation, not a configuration toggle.

Other custom features

The vendor states that "any other custom features" can be delivered by its development team, with ongoing support. That's an open-ended category, so the useful move is to map your requirements against the standard list above and route anything unmatched into a custom-scope discussion.

How to decide

If your needs sit entirely within the standard feature list, the base SDK is the straightforward path. If any requirement touches DRM, advanced EPUB 3 behavior, or something not listed, start a scoping conversation early — these affect architecture, timeline, and cost, and the page does not publish pricing or terms for custom work.