Preparing for Release 1.0.0

[DevSrSouza]

• Creates and moves ScreenModel API to it own module.
• Remove deprecated functions
• Add binary compatibility validator
• Remove Androidx module and AndroidScreen
• Promote Experimental APIs to Stable (removing the annotation)
• Generate the API Dump

[nvkleban]

Why AndroidScreen was removed in samples? Will be there any replacement of it and it's ScreenLifecycleProvider implementation?

[Syer10]

The AndroidScreenLifecycle is now default for all screens on Android, has been for the last few builds.

[DevSrSouza]

Import to notice here is that: for folks that are using blinding AndroidScreen there will be a single behavior change comparing it with Screen.
Currently AndroidScreen holds a unique Id for each new instance of the Screen, this is already documented usage of the library and will be documented in the future "Migration guides".

But how @Syer10 point out, the ScreenLifecycleProvider behavior that AndroidScreen had, is no longer required anymore, is the default behavior for all screen.

[nvkleban]

Thank you for the clarification!

[DevNatan]

@DevSrSouza can we take a look in TabOptions api design? the current design has "expected standards" for Android like title and icon but Voyager doesn't have this anywhere else in the API anymore.

And it's also a little complicated to create these options like indeX that we dont have inside the screen, this should be done by the developer from the outside. Should we see this before the release or can it be done later in a backwards compatible way?

See #141

[DevSrSouza]

@DevSrSouza can we take a look in TabOptions api design? the current design has "expected standards" for Android like title and icon but Voyager doesn't have this anywhere else in the API anymore.

And it's also a little complicated to create these options like indeX that we dont have inside the screen, this should be done by the developer from the outside. Should we see this before the release or can it be done later in a backwards compatible way?

See #141

Yes, we can look into this in next versions and also be backwards compatible.