Documentation
Learn how to convert, build, and scale your mobile applications using the Teznative engine.
We just released v2.1.0 with improved splash screen customization and faster build times.
Overview
Teznative is a powerful build engine that transforms any responsive website into a high-performance native mobile application. Unlike simple wrappers, our technology optimizes rendering, handles native transitions, and provides a robust bridge for device-level API access.
Quickstart Guide
Follow these four simple steps to get your mobile app ready for testing and publication.
1. Enter your URL
Start by entering the URL of your existing web application or website. Our engine will analyze the URL to ensure it's responsive and ready for mobile conversion.
2. Configure Branding
Upload your app icon (1024x1024px) and splash screen. Choose your primary brand colors which will be used for the native status bar and loading indicators.
3. Select Native Features
Enable features like Push Notifications, Biometric Auth, or Camera access via our simple checkbox interface. Our engine automatically injects the necessary native code.
4. Build & Download
Click "Build App" and our cloud servers will compile your binaries. You'll receive an APK for Android and a simulator-ready build for iOS within minutes.
System Requirements
Before you begin, ensure your web application meets the following criteria for the best native experience.
- Responsive Design: Your site must be mobile-friendly and use modern CSS (Flexbox/Grid).
- HTTPS Required: For security and native API access, your URL must use a valid SSL certificate.
- Performance: First Contentful Paint (FCP) should be under 1.5 seconds for a native feel.
Push Notifications
Teznative uses OneSignal for high-reliability push notifications. You can send marketing alerts, transactional updates, or personalized news directly to your users.
Configuration
Enter your OneSignal App ID in the Teznative dashboard. Once configured, you can trigger notifications from your backend using our API.
Device Permissions
Accessing native hardware requires explicit user permission. Our engine handles the complex permission request flow for you.
| Feature | Key | Usage Description |
|---|---|---|
| Camera | camera |
For profile photos and scanning. |
| Location | location |
For maps and local content. |
| Microphone | audio |
For voice search and calls. |
JS Bridge API
Communicate between your web code and the native mobile environment using our lightweight JavaScript bridge.
Installation
Example Usage
Play Store Setup
To publish on Google Play, you need a Google Developer Account and a signed AAB file from Teznative.
- Download your AAB binary from the dashboard.
- Create a new app in the Google Play Console.
- Upload the AAB to the Internal Testing track first.
- Complete the app content declaration (Target audience, Data safety, etc).
App Store Setup
Apple requires a more rigorous review process. Ensure your app provides value beyond a simple website wrapper.
- Register for the Apple Developer Program ($99/year).
- Create an App ID and Provisioning Profile.
- Upload your IPA via Transporter or Xcode.
- Submit for App Review (takes 24-48 hours).