Android twilio size apk

Содержание

APK размер, Twilio, разделение и совместимость архитектур
1 ответ
Похожие вопросы:
Measure the App Size Impact of Android Libraries
Measure up
Android twilio size apk

APK размер, Twilio, разделение и совместимость архитектур

Какие архитектуры должны быть размещены в splits.abi build.gradle? Я компилирую, используя только «armeabi-v7a», потому что использование всех собственных библиотек для всех архитектур генерирует очень большой APK. Я использую Proguard. Но я боюсь, что использование только «armeabi-v7a» может принести много проблем с совместимостью.

Для каждой архитектуры я получаю 3 файла .so внутри моей папки lib/: libclient.so, libtwilio-rtd-native.so и libtwilio_common_android_so. Приблизительно, 9 МБ foreach архитектуры = 36 МБ.

Возникает вопрос: А как насчет пользователей с устройствами и другими архитектурами?

1 ответ

Я создал совершенно новое приложение rails 5, в котором не было ничего, кроме скелета. Когда я создал простой контроллер приветствия/домашнюю страницу, сервер работал нормально. Но когда я добавил gem ‘twilio-ruby’ в свое приложение, все сломалось. Я не мог запустить сервер, я не мог создать.

Я занят добавлением файлов FFmpegMediaMetadataRetriever pre-build .aar в свой проект, чтобы уменьшить размер файла Apk для каждой архитектуры. Этот пост добавил следующее к его Gradle : android < splits < // Configures multiple APKs based on ABI. abi < // Enables building multiple APKs per ABI.

В конечном счете это сводится к вашим собственным потребностям. Мы предоставляем SDK для armeabi , armeabi-v7a , arm64-v8a , x86 и x86-64 . Вы сами решаете, для каких архитектур вы хотите скомпилировать, каждая из которых имеет плюсы (меньший размер APK) и минусы (потеря потенциальных установок), зависит от вас.

Вообще говоря, armeabi -это для старых устройств ( armeabi-v7a -для (2010-2014) и arm64-v8a (2015+). И x86* -это растущий сегмент.

Вы также можете рассмотреть возможность разделения APK, если размер является проблематичным: https://developer.android.com/studio/build/configure-apk-splits.html

Measure the App Size Impact of Android Libraries

Users – especially those with pay-per-byte mobile plans – will avoid downloading Android applications if they are too large. As a result, managing your Android application size helps ensure that users are not deterred from trying out your application. Google provides great strategies for reducing your application size, but many applications depend on third-party libraries which may not consider their app size impact.

Here at Twilio we understand this challenge, which is why we publish the app size impact of our Voice and Video Android SDKs with every release. Our CI pipeline contains a size measurement step, so we ensure that we do not introduce any unexpected size regressions during the development process.

Today, we are happy to announce that we have open sourced the utility we use to measure the size of our Android SDKs: apkscale.

Measure up

Apkscale is a Gradle plugin that helps measure the app size impact of Android libraries. The plugin is designed for Android library developers who would like to measure the size of their libraries directly from their projects. The snippets below provide the steps to include apkscale in your project.

Add this to buildscript section:

Apply the plugin in your Android library project:

Источник

Android twilio size apk

Twilio Video Quickstart for Android

Get started with Video on Android:

Quickstart — Run the quickstart app
Examples — Customize your video experience with these examples
Using an Emulator — Setup an emulator in Android Studio
Reducing APK Size — Use ABI splits to reduce your APK size
Troubleshooting Audio — Mitigate audio issues in your application
Rendering Video — A guide to rendering video in your application
Setup an Access Token Server — Setup an access token server
More Documentation — More documentation related to the Video Android SDK
Issues & Support — Filing issues and general support

To get started with the Quickstart application follow these steps:

Open this project in Android Studio and select the quickstart or quickstartKotlin app module.

Generate an Access Token

View instructions here for how to generate an Access Token using the Twilio CLI. Generating Access Tokens with the Twilio CLI is a quick way to get an Access Token for testing and development purposes.

Add the access token string copied from the console to a variable named TWILIO_ACCESS_TOKEN in your local.properties file.

Run the quickstart app on an Android device or Android emulator.

Press the video call button at the bottom right portion of the screen and type a room name to connect to a Room.

On another device, use an additional access token with a different identity to connect to the same room.

In addition to the quickstart we’ve also added a few examples of use cases that show you how to create and customize your media as follows:

Custom Video Capturer — Demonstrates how a custom VideoCapturer can be implemented to capture the contents of a View .
Custom Video Sink — Demonstrates how to implement a custom tvi.webrtc.VideoSink that captures a Bitmap of the last rendered frame.
Screen Capturer — Demonstrates how to use the screen capturer.
Advanced Camera Capturer — Demonstrates advanced use cases of CameraCapturer like injecting custom camera parameters and taking a picture.
Video Invite — Demonstrates how to use Twilio Notify to invite other participants to a room.
Data Tracks — Demonstrates how to use DataTrack s to write a simple collaborative drawing app.
Audio Sink — Demonstrates writing raw PCM audio to a .wav file from a RemoteAudioTrack using AudioSink .
Collaboration App — A collaboration app that demonstrates how to use the Room API for multiparty conferencing.

Using an Emulator

This guide will walk you through setting up an emulator that is compatible with the Video SDK.

Open Android Studio and navigate to Tools → Android → AVD Manager.

Читайте также: Android app step by step

2. Create a virtual device.

3. Select your desired device.

4. Select a system image. We recommend either x86 or x86_64 images.

5. Click “Show Advanced Settings” and we recommend setting both cameras as “Emulated”. Note that other camera configurations will work with the exception of setting both cameras as “webcam()”.

6. Configure the rest of your device accordingly and click “Finish”.

Reducing APK Size

Our library is built using native libriares. As a result, if you use the default gradle build you will generate an APK with all four architectures(armeabi-v7a, arm64-v8a, x86, x86_64) in your APK.

APK splits allow developers to build multiple APKs for different screen sizes and ABIs. Enabling APK splits ensures that the minimum amount of files required to support a particular device are packaged into an APK.

The following snippet shows an example build.gradle with APK splits enabled.

The adoption of APK splits requires developers to submit multiple APKs to the Play Store. Refer to Google’s documentation for how to support this in your application.

The following sections provide guidance on how to ensure optimal audio quality in your applications. Results may vary when using APIs within the org.webrtc package. While we expose these APIs we do not actively test their usage.

Managing Audio Devices with AudioSwitch

The Java and Kotlin quickstarts use AudioSwitch to control audio focus and manage audio devices within the application. If you have an issue or question related to audio management, please open an issue in the AudioSwitch project.

Configuring Hardware Audio Effects

Our library performs acoustic echo cancellation (AEC), noise suppression (NS), and auto gain control (AGC) using device hardware by default. Using device hardware is more efficient, but some devices do not implement these audio effects well. If you are experiencing echo, background noise, or unexpected volume levels on certain devices reference the following snippet for enabling software implementations of AEC, NS, and AGC.

Configuring OpenSL ES

Our library does not use OpenSL ES for audio playback by default. Some prior versions starting with Video Android SDK 5.5.1 did use OpenSL ES by default. Using OpenSL ES is more efficient, but can cause problems with other audio effects. For example, we found on the Nexus 6P that OpenSL ES affected the device’s hardware echo canceller so we blacklisted the Nexus 6P from using OpenSL ES. If you are experiencing audio problems with a device that cannot be resolved using software audio effects, reference the following snippet for enabling OpenSL ES:

Managing Device Specific Configurations

The Video Android SDK does not maintain a list of devices for which hardware effects or OpenSL ES are disabled. We recommend maintaining a list in your own application and disabling these effects as needed. The Signal App provides a great example of how to maintain a list and disable the effects as needed.

Using the following WebRTC based acoustic echo canceler on the Pixel 3 XL will disable the microphone system wide.
Usage: WebRtcAudioUtils.setWebRtcBasedAcousticEchoCanceler(true);
A bug has been filed with WebRTC and can be found here.

A VideoTrack can be rendered in your application using addRenderer which takes an implementation of VideoRenderer . A VideoRenderer is most commonly used to render video to a UI, but could be used for other scenarios such as rendering to a file. The following section provides guidance on how to render video in your application.

Working with VideoView

For simply rendering video to your application’s UI, we recommend using VideoView . VideoView extends SurfaceView and can be added to your view hierarchy in a layout file or programmatically. To render a VideoTrack to a VideoView simply call videoTrack.addRenderer(videoView) . The following snippets demonstrate how to setup the a thumbnail video overlayed on a primary video as seen in the screenshot below.

VideoView in a Layout File

Adding VideoView Programmatically

Custom Renderers and I420Frame

For advanced use cases you can provide a custom VideoRenderer where your custom renderer will be provided with an I420Frame to render. An I420Frame can be represented with a ByteBuffer array of Y, U, and V pixel data with an array of strides for each plane or as a texture. When a frame is represented as a texture, I420Frame#textureId will be set to a positive non zero value with I420Frame#yuvPlanes and I420Frame#yuvStrides set to null . The YUV data can be extracted from the texture using an instance of org.webrtc.YuvConverter and the I420Frame#samplingMatrix . When a frame is represented as an array of ByteBuffer , I420Frame#textureId will be 0, I420Frame#yuvPlanes contains the YUV pixel data, and I420Frame#yuvStrides contains each plane’s stride. For an example of implementing a custom VideoRenderer we recommend referencing the Custom Video Renderer module.

Setup an Access Token Server

Using Twilio’s Video client within your applications requires an access token.

You can run your own server that provides access tokens, based on your Twilio credentials. This server can either run locally on your development machine, or it can be installed on a server. If you run the server on your local machine, you should use the ngrok utility to give the server an externally accessible web address. That way, you can run the quickstart app on an Android device.

Configuring the Access Token Server

If you want to be a little closer to a real environment, you can download one of the video quickstart applications — for instance, Video Quickstart: Node and either run it locally, or install it on a server.

You’ll need to gather a couple of configuration options from your Twilio developer console before running it, so read the directions on the quickstart. You’ll copy the .env.example file to a .env file, and then add in these credentials:

Credential	Description
Twilio Account SID	Your main Twilio account identifier — find it on your dashboard.
API Key	Used to authenticate — generate one here.
API Secret	Used to authenticate — just like the above, you’ll get one here.

A Note on API Keys

When you generate an API key pair at the URLs above, your API Secret will only be shown once — make sure to save this in a secure location.

Running the Video Quickstart with ngrok

If you run your video chat application on an Android device, you’ll need to provide an externally accessible URL for the app. The ngrok tool creates a publicly accessible URL that you can use to send HTTP/HTTPS traffic to a server running on your localhost. Use HTTPS to make web connections that retrieve a Twilio access token.

When you get a URL from ngrok, go ahead and update local.properties. Reference the following snippet.

You can find more documentation on getting started as well as our latest Javadoc below:

Issues and Support

Please file any issues you find here on Github. Please ensure that you are not sharing any Personally Identifiable Information(PII) or sensitive account information (API keys, credentials, etc.) when reporting an issue.

For general inquiries related to the Video SDK you can file a support ticket

Источник

Android twilio size apk

APK размер, Twilio, разделение и совместимость архитектур

1 ответ

Похожие вопросы:

Measure the App Size Impact of Android Libraries

Measure up

Android twilio size apk