doc: clarify encoding bundle versions

Author: ChALkeR

README.md

@@ -100,29 +100,44 @@ _These are only provided as a compatibility layer, prefer hardened APIs instead
 
 ### Lite version
 
-If you don't need support for legacy multi-byte encodings, you can use the lite import:
-```js
-import { TextDecoder, TextEncoder } from '@exodus/bytes/encoding-lite.js'
-import { TextDecoderStream, TextEncoderStream } from '@exodus/bytes/encoding-lite.js' // Requires Streams
-```
+Alternate exports exist that can help reduce bundle size:
+
+  * `@exodus/bytes/encoding-browser.js` - resolves to a tiny import in browser bundles, preferring native `TextDecoder` / `TextEncoder`.
+    For non-browsers (Node.js, React Native), loads a full implementation.
+
+  * `@exodus/bytes/encoding-lite.js` - if you don't need support for legacy multi-byte encodings.
 
-This reduces the bundle size 9x:\
-from 94 KiB gzipped for `@exodus/bytes/encoding.js` to 10 KiB gzipped for `@exodus/bytes/encoding-lite.js`.\
-(For comparison, `text-encoding` and `iconv-lite` are each over 195 KiB gzipped):
+    ```js
+    import { TextDecoder, TextEncoder } from '@exodus/bytes/encoding-lite.js'
+    import { TextDecoderStream, TextEncoderStream } from '@exodus/bytes/encoding-lite.js' // Requires Streams
+    ```
 
+    Reduces the bundle size 9x, while still keeping `utf-8`, `utf-16le`, `utf-16be` and all single-byte encodings specified by the spec.
+    The only difference is support for legacy multi-byte encodings.
+
+    See [the list of encodings](https://encoding.spec.whatwg.org/#names-and-labels).
+
+    This can be useful for example in React Native global TextDecoder polyfill,
+    if you are sure that you don't need legacy multi-byte encodings support.
+
+
+Bundle size comparison:
 | import | size |
 | - | - |
 | `@exodus/bytes/encoding-browser.js` | <sub>![](https://img.shields.io/bundlejs/size/@exodus/bytes/encoding-browser.js?style=flat-square)</sub> |
 | `@exodus/bytes/encoding-lite.js` | <sub>![](https://img.shields.io/bundlejs/size/@exodus/bytes/encoding-lite.js?style=flat-square)</sub> |
 | `@exodus/bytes/encoding.js` | <sub>![](https://img.shields.io/bundlejs/size/@exodus/bytes/encoding.js?style=flat-square)</sub> |
 | `text-encoding` | <sub>![](https://img.shields.io/bundlejs/size/text-encoding?style=flat-square)</sub> |
-| `iconv-lite` | <sub>![](https://img.shields.io/bundlejs/size/iconv-lite?style=flat-square)</sub> |
+| `iconv-lite` | <sub>![](https://img.shields.io/bundlejs/size/iconv-lite/lib/index.js?style=flat-square)</sub> |
 | `whatwg-encoding` | <sub>![](https://img.shields.io/bundlejs/size/whatwg-encoding?style=flat-square)</sub> |
 
-It still supports `utf-8`, `utf-16le`, `utf-16be` and all single-byte encodings specified by the spec,
-the only difference is support for legacy multi-byte encodings.
+In general:
+
+ 1. Libraries are advised to use single-purpose hardened `@exodus/bytes/utf8.js` / `@exodus/bytes/utf16.js` APIs for Unicode or
+ global `TextDecoder` for the remaining WHATWG encodings
 
-See [the list of encodings](https://encoding.spec.whatwg.org/#names-and-labels).
+ 2. Applications (including React Native apps) are advised to load either `@exodus/bytes/encoding-lite.js` or `@exodus/bytes/encoding.js`
+ (depending on whether legacy multi-byte support is needed) and use that a a global polyfill.
 
 ## API