Skip to main content

Release Notes

This document tracks the release history and notable changes for the Entrupy Android SDK.

Version 1.0.0 (Initial Release)

Release Date: Q4 2025 (Planned)

Features

  • Initial release of the Entrupy Android SDK
  • Full-screen Capture Flow for item authentication
  • Detail View for displaying authentication results
  • Multi-language support (English, Japanese, Traditional Chinese, Simplified Chinese)
  • On-device AI for enhanced capture quality
  • Secure user authorization system
  • Support for Android API 24+ (Android 7.0 Nougat and above)

SDK Components

  • Capture Flow: Guided photo capture with real-time quality feedback
  • Detail View: Comprehensive authentication result display
  • Authorization System: Secure token-based user authentication
  • Configuration Management: Dynamic SDK configuration loading

Technical Specifications

  • Minimum SDK Version: API 24 (Android 7.0 Nougat)
  • Target SDK Version: API 35 (Android 15)
  • Distribution: Maven Central
  • Package Name: com.entrupy:sdk

Integration Requirements

  • Android Studio 4.0+
  • Gradle 7.0+
  • Kotlin 1.5+ (recommended) or Java 8+
  • Internet connectivity for SDK operations
  • Camera and storage permissions

Known Limitations

  • Requires user authorization before any SDK operations
  • Capture sessions timeout after 2 hours of inactivity
  • Network connectivity required for all operations
  • Some features may require specific Android versions

Breaking Changes

  • N/A (Initial release)

Deprecations

  • N/A (Initial release)

Upcoming Releases

Version 1.1.0 (Planned)

  • Enhanced error handling and recovery
  • Improved offline support
  • Additional customization options
  • Performance optimizations

Version 1.2.0 (Planned)

  • Advanced analytics and reporting
  • Extended language support
  • Additional authentication methods
  • Enhanced security features

Support

For technical support, bug reports, or feature requests, please contact:

Migration Guide

This is the initial release, so no migration is required. Future releases will include migration guides for existing integrations.