Skip to content

Commit d404d98

Browse files
committed
Vale edits
1 parent bcc0f9a commit d404d98

File tree

1 file changed

+10
-10
lines changed
  • src/connections/sources/catalog/libraries/mobile/kotlin-android

1 file changed

+10
-10
lines changed

src/connections/sources/catalog/libraries/mobile/kotlin-android/index.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ With Analytics-Kotlin, you can send data using Kotlin applications to any analyt
1616
If you're migrating to Analytics-Kotlin from a different mobile library, you can skip to the [migration guide](/docs/connections/sources/catalog/libraries/mobile/kotlin-android/migration/).
1717

1818

19-
## Getting Started
19+
## Getting started
2020

2121
To get started with the Analytics-Kotlin mobile library:
2222

@@ -91,10 +91,10 @@ To get started with the Analytics-Kotlin mobile library:
9191
5. Enable Java 8+ API desugaring.
9292
9393
The SDK internally uses a number of Java 8 language APIs through desugaring. Make sure your project either [enables desugaring](https://developer.android.com/studio/write/java8-support#library-desugaring)) or requires a minimum API level of 26.
94-
95-
Configuration options such as IDFA collection and automatic screen tracking are found in Segment’s Plugin Examples repo - https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app/src/main/java/com/segment/analytics/next/plugins
9694
97-
## Tracking Methods
95+
Configuration options such as IDFA collection and automatic screen tracking are found in Segment’s [Plugin Examples repository](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app/src/main/java/com/segment/analytics/next/plugins){:target="_blank"}.
96+
97+
## Tracking methods
9898
9999
Once you've installed the mobile or server Analytics-Kotlin library, you can start collecting data through Segment's tracking methods:
100100
- [Identify](#identify)
@@ -155,7 +155,7 @@ analytics.track("View Product", buildJsonObject {
155155
### Screen
156156
The [Screen](/docs/connections/spec/screen/) method lets you record whenever a user sees a screen in your mobile app, along with optional extra information about the page being viewed.
157157

158-
You'll want to record a screen event whenever the user opens a screen in your app. This could be a view, fragment, dialog or activity depending on your app.
158+
You'll want to record a screen event whenever the user opens a screen in your app. This could be a view, fragment, dialog, or activity depending on your app.
159159

160160
Not all integrations support screen, so when it's not supported explicitly, the screen method tracks as an event with the same parameters.
161161

@@ -205,10 +205,10 @@ analytics.group("user-123", buildJsonObject {
205205
{% endcodeexampletab %}
206206
{% endcodeexample %}
207207

208-
## Plugin Architecture
208+
## Plugin architecture
209209
Segment's plugin architecture enables you to modify and augment how the analytics client works. From modifying event payloads to changing analytics functionality, plugins help to speed up the process of getting things done.
210210

211-
Plugins are run through a timeline, which executes in order of insertion based on their entry types. Segment has these 5 entry types:
211+
Plugins are run through a timeline, which executes in order of insertion based on their entry types. Segment has these five entry types:
212212

213213
| Type | Details |
214214
| ------------- | ---------------------------------------------------------------------------------------------- |
@@ -219,7 +219,7 @@ Plugins are run through a timeline, which executes in order of insertion based o
219219
| `utility` | Executes only with manual calls such as Logging. |
220220

221221
### Fundamentals
222-
There are 3 basic types of plugins that you can use as a foundation for modifying functionality. They are: [`Plugin`](#plugin), [`EventPlugin`](#eventplugin), and [`DestinationPlugin`](#destinationplugin).
222+
There are three basic types of plugins that you can use as a foundation for modifying functionality. They are: [`Plugin`](#plugin), [`EventPlugin`](#eventplugin), and [`DestinationPlugin`](#destinationplugin).
223223

224224
#### Plugin
225225
`Plugin` acts on any event payload going through the timeline.
@@ -343,7 +343,7 @@ analytics.add(yourPlugin)
343343
See how different platforms and languages use Analytics-Kotlin in different [example projects](https://github.com/segmentio/analytics-kotlin/tree/main/samples).
344344
The example projects contain sample [plugins](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app/src/main/java/com/segment/analytics/next/plugins) and [destination plugins](https://github.com/segmentio/analytics-kotlin/tree/main/samples/kotlin-android-app-destinations/src/main/java/com/segment/analytics/destinations/plugins) you can utilize.
345345

346-
## Utility Methods
346+
## Utility methods
347347
The Analytics-Kotlin utility methods help you work with plugins from the analytics timeline. They include:
348348
- [Add](#add)
349349
- [Find](#find)
@@ -442,7 +442,7 @@ analytics.reset()
442442
{% endcodeexampletab %}
443443
{% endcodeexample %}
444444

445-
## Build Your Own Destination
445+
## Build Your own destination
446446

447447
If Segment doesn't support your Kotlin destination, you can build your own with the template Segment provides.
448448

0 commit comments

Comments
 (0)