[WooPos][Non Simple Product types] Retry UI for pagination errors on variations screens #12972

AnirudhBhat · 2024-11-21T09:56:20Z

Description

This PR adds a new UI for retrying errors during paginating variations.

Along with this, this PR also does a couple of small changes:

In totals screen after payment is success. It navigates the screen back to items list screen so that when we click on "new order" button from the payment success screen, we end up on the items list screen instead of variations screen if we had proceeded to totals screen from variations screen.

Changes the messages which previously only mentioned only simple physical products can be added in POS. After this PR, it should say simple physical and variable products can be added. Below are the places where this got changed:

Banner above the items list in items screen
On clicking learn more in the banner, a dialog pops up with more information. The changes should reflect here as well
When there are no products compatible for POS, we show an empty state. The changes should reflect here as well

Design

Implementation

Testing information

Retry pagination UI

Navigate to POS mode (more menu -> POS)
Click on any variable products that has more than 10 variations
Ensure you navigate to the variations screen
Turn on airplane mode
Scroll down
Ensure you see the pagination error UI
Click on retry and ensure nothing happens as we are still in airplane mode
Turn off airplane mode
Now, click on retry button again
Ensure the variations gets loaded

Navigate to items list after payment success

Navigate to POS mode (more menu -> POS)
Add products to cart
Navigate to variations screen before checking out
Ensure payment is success
Click on "New Order" button
Ensure you navigate to items list screen.

Changes to messages

Navigate to POS mode (more menu -> POS)
Ensure you see a banner that says both simple and variable products instead of just simple products
Click on learn more in the banner
Ensure the dialog also mentions both simple and variable products
Navigate to POS mode where there are no compatible products to display (no simple and variable products)
Ensure the empty state also says that only simple and variable products are compatible.

The tests that have been performed

Tested on both light and dark modes

Images/gif

pagination_retry_ui.mp4

I have considered if this change warrants release notes and have added them to RELEASE-NOTES.txt if necessary. Use the "[Internal]" label for non-user-facing changes.

Reviewer (or Author, in the case of optional code reviews):

Please make sure these conditions are met before approving the PR, or request changes if the PR needs improvement:

The PR is small and has a clear, single focus, or a valid explanation is provided in the description. If needed, please request to split it into smaller PRs.
Ensure Adequate Unit Test Coverage: The changes are reasonably covered by unit tests or an explanation is provided in the PR description.
Manual Testing: The author listed all the tests they ran, including smoke tests when needed (e.g., for refactorings). The reviewer confirmed that the PR works as expected on big (tablet) and small (phone) in case of UI changes, and no regressions are added.

…new order button will take us to items list screen instead of variations screen if the user proceeded to checkout while they were in variations screen.

…ccess

dangermattic · 2024-11-21T09:58:25Z

	3 Errors
🚫	Please add tests for class `VariationsLRUCache` (or add `unit-tests-exemption` label to ignore this).
🚫	This PR is tagged with `status: do not merge` label(s).
🚫	PR is not assigned to a milestone.

	1 Warning
⚠️	This PR is larger than 300 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.

Generated by 🚫 Danger

wpmobilebot · 2024-11-21T10:02:38Z

📲 You can test the changes from this Pull Request in WooCommerce-Wear Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce-Wear Android
	Platform	⌚️ Wear OS
	Flavor	Jalapeno
	Build Type	Debug
	Commit	`bd39579`
	Direct Download	`woocommerce-wear-prototype-build-pr12972-bd39579.apk`

wpmobilebot · 2024-11-21T10:14:30Z

📲 You can test the changes from this Pull Request in WooCommerce Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce Android
	Platform	📱 Mobile
	Flavor	Jalapeno
	Build Type	Debug
	Commit	`bd39579`
	Direct Download	`woocommerce-prototype-build-pr12972-bd39579.apk`

codecov-commenter · 2024-11-21T10:21:46Z

Codecov Report

Attention: Patch coverage is 52.77778% with 17 lines in your changes missing coverage. Please review.

Project coverage is 39.63%. Comparing base (3be8fe3) to head (e40c789).

Files with missing lines	Patch %	Lines
...ce/android/ui/woopos/home/items/WooPosItemsList.kt	0.00%	10 Missing ⚠️
...home/items/variations/WooPosVariationsViewModel.kt	63.15%	1 Missing and 6 partials ⚠️

Additional details and impacted files

@@                            Coverage Diff                             @@
##             issue/12846-analytics-for-variations   #12972      +/-   ##
==========================================================================
- Coverage                                   39.63%   39.63%   -0.01%     
+ Complexity                                   5973     5972       -1     
==========================================================================
  Files                                        1268     1268              
  Lines                                       73276    73285       +9     
  Branches                                    10057    10061       +4     
==========================================================================
+ Hits                                        29041    29043       +2     
- Misses                                      41656    41661       +5     
- Partials                                     2579     2581       +2

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

kidinov · 2024-11-21T11:40:49Z

@AnirudhBhat 👋

Where does this design come from? IMO, it doesn't match expectations from this kind of UX in a mobile app.

I believe this should have:

The same height as a normal item
Just one line: icon | text | button
When the button is clicked, we replace that with the "loading indicator" list item till the response comes

Something like that maybe?

@malinajirka @samiuelson wdyt?

AnirudhBhat · 2024-11-22T03:48:45Z

Where does this design come from? IMO, it doesn't match expectations from this kind of UX in a mobile app.

I believe this should have:

The same height as a normal item
Just one line: icon | text | button
When the button is clicked, we replace that with the "loading indicator" list item till the response comes
Something like that maybe?

Wagner gave the designs and we had conversation about this on Slack here

IMHO, I don't see any problem with this design and I don't feel it deviates from the mobile UX especially considering that this is run only on tablet devices.

Clarity: It provides a clear, standalone visual for errors, which ensures users can immediately understand what went wrong.
Consistency: It aligns with the rest of our app's (POS) error screens, it maintains uniformity and helps users understand that something went wrong quickly.
Prominent Call to Action: The "Retry" button is clearly visible and easy to tap - as this was something we considered for POS that CTAs should be big and easily tappable considering our use case is for the POS.

If we show the error as another card with the same height as rest of the items. I can see few confusions that could arise:

Clarity: On a quick glance, as the user will be scrolling, it's hard to understand what happened. Whether a new item got loaded or was it an error.
Inconsistency: The way we show the error here is inconsistent with the rest of the screens on our POS system.
Confusion: The card-style error display, with the same height as a list item, might create confusion by making it appear as though only one item failed to load, rather than multiple items or the entire batch.

What do you think?

…where it said we support only simple physical products.

malinajirka · 2024-11-22T07:49:22Z

I lean towards the approach Andrei mentioned (mostly because it's a standard behavior across apps on Android), but it's ultimately Wagner's decision, so I'd defer this to him.

One thing which feels broken is the animation that happens after you tap on Retry in the video - I'm not even sure, if more items loaded or if just the scrolling position changed. If we decide to go with this current approach, I think we need to polish it. If we decide to go with Andrei's approach, this problem disappears as the item will be replaced with the existing shimmer effect row so there won't be any change in the scrolling position at all.

kidinov · 2024-11-22T09:26:07Z

@AnirudhBhat 👋

Clarity: It provides a clear, standalone visual for errors, which ensures users can immediately understand what went wrong.

With the item being so big, I have doubts that people will even understand what's going on, as your synthetical example is not what people will have. They will have a list of 20 or more products. They will scroll down where they will see an item with a shimmer effect, which after some time is replaced by a huge thing, but that huge thing won't be visible automatically. They will see, in most cases, just empty space at the bottom People will need to figure out that they need to scroll down more to find this "retry" button, and there is no necessity at all to have that thing so huge and so not in line with the rest of the items. On top of that the animation looks really wrong when things are that huge.

And again, this is completely not what people got used to see in mobile apps, so clarity is really questionable here

Consistency: It aligns with the rest of our app's (POS) error screens, it maintains uniformity and helps users understand that something went wrong quickly.

But this is not an error screen at all. It's a contextual error. People can easily keep using the shown products if the next page is not loaded

Prominent Call to Action: The "Retry" button is clearly visible and easy to tap - as this was something we considered for POS that CTAs should be big and easily tappable considering our use case is for the POS.

The button in the item can be as huge as we want/need

Looking into Figma design, I feel that there is a misunderstanding on the flow. In 2 out of 3 designs, there are no products shown at all. I'll ask Wagner to reconsider

kidinov · 2024-11-22T09:40:18Z

WooCommerce/src/main/kotlin/com/woocommerce/android/ui/woopos/home/items/WooPosBaseViewState.kt

@@ -8,4 +8,5 @@ interface ContentViewState {
    val items: List<WooPosItem>
    val loadingMore: Boolean
    val reloadingProductsWithPullToRefresh: Boolean
+    val errorLoadingMoreItems: Boolean


The state defined like that can contain invalidate states, e.g. loadingMore = true and errorLoadingMoreItems = true.

We probably should do something like

val paginationIndicator: PaginationIndicator enum PaginationIndicator { Loading, Error, None }

By the way, ContentViewState does not follow the naming convention of the top-level classes. It probably should be WooPosItemsViewState. And there are a few more, e.g., ToolbarAccessibilityLabels, for instance. And some classes that are in the items package now, e.g., WooPosBanner should either contain an item in them or be placed in another package

Thanks for raising this. I had this on my list to refactor hence I kept the PR as draft. Here's the refactored state: a45bd6c

kidinov · 2024-11-22T15:31:31Z

...ain/kotlin/com/woocommerce/android/ui/woopos/home/items/variations/WooPosVariationsScreen.kt

+            .padding(
+                start = 16.dp.toAdaptivePadding(),
+                end = 16.dp.toAdaptivePadding(),
+                top = 30.dp.toAdaptivePadding(),


I think 30 can not be in 4dp grid. 28 or 32 should be

https://m2.material.io/design/layout/spacing-methods.html#baseline-grid

Done: 71ee602

kidinov · 2024-11-22T15:35:10Z

.../kotlin/com/woocommerce/android/ui/woopos/home/items/variations/WooPosVariationsViewModel.kt

@@ -100,18 +93,15 @@ class WooPosVariationsViewModel @Inject constructor(
        if (!variationsDataSource.canLoadMore()) {
            return
        }
-        _viewState.value = currentState.copy(loadingMore = true)
+        _viewState.value = currentState.copy(loadingMore = true, errorLoadingMoreItems = false)
        loadMoreJob?.cancel()
        loadMoreJob = viewModelScope.launch {
            val result = variationsDataSource.loadMore(productId)
            if (result.isSuccess) {
                Result.success(Unit)


What does this line do?

This is no longer relevant as result of this change: a45bd6c

kidinov · 2024-11-22T15:35:54Z

.../kotlin/com/woocommerce/android/ui/woopos/home/items/variations/WooPosVariationsViewModel.kt

@@ -100,18 +93,15 @@ class WooPosVariationsViewModel @Inject constructor(
        if (!variationsDataSource.canLoadMore()) {
            return
        }
-        _viewState.value = currentState.copy(loadingMore = true)
+        _viewState.value = currentState.copy(loadingMore = true, errorLoadingMoreItems = false)
        loadMoreJob?.cancel()
        loadMoreJob = viewModelScope.launch {
            val result = variationsDataSource.loadMore(productId)
            if (result.isSuccess) {


np:

_viewState.value = if (result.isSuccess) { currentState.copy(loadingMore = false, errorLoadingMoreItems = false) } else { currentState.copy(loadingMore = false, errorLoadingMoreItems = true) }

kidinov · 2024-11-22T15:37:47Z

.../kotlin/com/woocommerce/android/ui/woopos/home/items/variations/WooPosVariationsViewModel.kt

        loadMoreJob?.cancel()
        loadMoreJob = viewModelScope.launch {
            val result = variationsDataSource.loadMore(productId)
            if (result.isSuccess) {
                Result.success(Unit)
-                if (!variationsDataSource.canLoadMore()) {
-                    _viewState.value = currentState.copy(loadingMore = false)


Can you use currentState here? _viewState.value can be modified by the time the request comes back but you copying based on the old state

This is no longer relevant as result of this change: a45bd6c

…ean value to minimise the occurence of invalid states

kidinov · 2024-12-05T14:14:42Z

.../kotlin/com/woocommerce/android/ui/woopos/home/items/variations/WooPosVariationsViewModel.kt

    private var loadMoreJob: Job? = null

-    fun init(productId: Long) {
-        fetchVariations(productId = productId, withPullToRefresh = false, withCart = true)
+    fun init(productId: Long, withPullToRefresh: Boolean = false, withCart: Boolean = true) {


Overall, have you explored the possibility of recreating this VM every time the variations are open? Now it seems very error prone as the state is kept for different lists of variations

I had and navigating to and from variation screen was causing problem. Problem in the sense that we need only left pane to change when coming back from variations screen but it was looking as if the whole screen was being popped out of the back stack. I've slightly modified and the View Model is recreated now for each variable product: 1718bb3

kidinov · 2024-12-05T14:40:58Z

@AnirudhBhat 👋

Looks much better!

You show old data for a second before it gets updated now

12-05--15-16.mp4

Sometimes it loads the next page but loads nothing:

12-05--15-20.mp4

Why page size is 10 items for variations, while for products 25? I know that you reuse the handler, but I am not sure that it should be different in our POS case

We won't load the next page if the response hasn't come back yet. It's tricky, but:

having 25 items page size would partially mitigate that
Or you actually know the exact size of the variation list, you can easily determine when the next page exists and when not without getting response

12-05--15-38.mp4

kidinov · 2024-12-05T14:44:25Z

.../main/kotlin/com/woocommerce/android/ui/products/variations/selector/VariationListHandler.kt

@@ -42,4 +41,8 @@ class VariationListHandler @Inject constructor(private val repository: Variation
            offset += PAGE_SIZE
        }.map { }
    }
+
+    fun resetLoadMoreState() {
+        canLoadMore = false


It looks like you modified the atomic var boolean from a different thread, which may lead to inconsistency. Check ProductListHandler

Having said that you may need determine if there is a next page based on specific products. Now it's shared state between different lists which may or already leads to issues

This is no longer needed. I've removed this method.

AnirudhBhat · 2024-12-06T08:02:43Z

@kidinov Thanks for your patience and the reviews. Much appreciated 🙇

You show old data for a second before it gets updated now

I couldn't reproduce this to be honest. This should be fixed now with view model being re-created for each variable product

Sometimes it loads the next page but loads nothing:

Can you please let me know the exact steps? I couldn't reproduce this either.

We won't load the next page if the response hasn't come back yet. It's tricky

I've set page size to 25 now and it should to some extent fix the issue. I'll come up with a separate PR to see how best to avoid this situation. I hope that's okay with you.

Also, can you please do another round of testing. Thanks!

kidinov · 2024-12-06T14:44:34Z

...rc/main/kotlin/com/woocommerce/android/ui/woopos/home/items/variations/VariationsLRUCache.kt

+import kotlinx.coroutines.sync.Mutex
+import kotlinx.coroutines.sync.withLock
+
+class VariationsLRUCache<K, V>(maxSize: Int) {


It looks like that most of the methods of this class are not used

Removed unnecessary methods: f1f54b0

kidinov · 2024-12-06T14:46:21Z

...kotlin/com/woocommerce/android/ui/woopos/home/items/variations/WooPosVariationsDataSource.kt

+    private val cacheMutex = Mutex()
+
+    private suspend fun getCachedVariations(productId: Long): List<ProductVariation> {
+        return cacheMutex.withLock { variationCache.get(productId) ?: emptyList() }


You have mutex here and you have another mutex on mutex inside of the cache

Remove unnecessary mutex locks: dfaa6fe

kidinov · 2024-12-06T14:57:35Z

@AnirudhBhat 👋

It seems mostly fine now. I left a couple of code-related comments, though

And I still have this very weird behavior with the pagination of the variations. Notice that the loading item disappears earlier sometimes, sometimes it doesn't appear at all . I'd suggest you to use https://github.com/woocommerce/wc-smooth-generator plugin and try different cases yourself with different amounts of variations to fix the issue

12-06--15-52.mp4

…w state if load more job is active

…tate if load more job is not active

# Conflicts: # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/woopos/home/items/variations/WooPosVariationsScreen.kt # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/woopos/home/totals/WooPosTotalsViewModel.kt # WooCommerce/src/test/kotlin/com/woocommerce/android/ui/woopos/home/totals/WooPosTotalsViewModelTest.kt

AnirudhBhat · 2024-12-09T05:32:05Z

@kidinov I was able to figure out the pagination edge case issue. Here's my understanding of the problem:

The issue occurs because when I open the variations screen, cached data is displayed first, and a background remote fetch is triggered to refresh the data. If I scroll to the bottom during this time, a loadMore operation is triggered to fetch the next page of variations, and the pagination loading state is displayed. However, when the initial remote fetch completes, it updates the view state and unintentionally resets the pagination loading state, making it look like nothing is happening. This is misleading because the loadMore operation is still in progress, and the user has to wait without any indication until the additional data is finally loaded.

This was reproducible on the products list as well.

pagination_products.mp4

I've made the changes and it should fix the problem. Please have a look.

kidinov · 2024-12-09T20:42:46Z

@AnirudhBhat

I still consistently can reproduce the issue

12-09--21-41.mp4

…the variations screen.

AnirudhBhat · 2024-12-10T04:02:46Z

@kidinov Can you please have a look now. Let me know if it's still reproducible and I'll probably create a new ticket for it and unblock this PR. Many thanks!

kidinov · 2024-12-11T09:48:25Z

@AnirudhBhat I could not able to reproduce the issue anymore

We'll need to implement the loading more error in this PR, though, as it is also used in products, right?

AnirudhBhat added 10 commits November 21, 2024 14:11

Add state to indicate error while paginating

bddcae5

Handle error while paginating in WooPosItemsList.kt

9873533

Handle error while paginating in WooPosItemsScreen.kt

42f4e1a

Remove snack bar implementation from WooPosVariationsScreen

0fe310a

Override errorloadingMoreItems property in variations view state

d84a3a8

Navigate to items list screen on payment success so that clicking on …

455d396

…new order button will take us to items list screen instead of variations screen if the user proceeded to checkout while they were in variations screen.

Add tests for different state updates while paginating

30b6d5d

Remove unnecessary padding from the variations screen

53a1838

Add test to verify we navigate to the items list screen on payment su…

bab7cbe

…ccess

Remove unused imports

8ceaa5f

AnirudhBhat added type: task An internally driven task. feature: point of sale POS project labels Nov 21, 2024

Make changes to string resource to include variable products as well …

e5f7823

…where it said we support only simple physical products.

kidinov reviewed Nov 22, 2024

View reviewed changes

AnirudhBhat added 4 commits November 25, 2024 10:34

Refactor pagination state logic. Use sealed interface instead of bool…

a45bd6c

…ean value to minimise the occurence of invalid states

Yse 32 instead of 30 dp.

71ee602

Use MutableStateFlow's atomic operation to update the view state

84febe1

fix detekt error

5b60693

kidinov reviewed Dec 5, 2024

View reviewed changes

AnirudhBhat added 8 commits December 6, 2024 10:17

Use SDK's in built LRU cache

2780766

Update variations page size to 25

f54516c

Remove unnecessary method

36b359b

Add key to hilt view model so that new instance is created for each key

1718bb3

Remove unnecessary methods

a61e5f6

Remove unnecessary val

bd3645a

Use import for Mutex

7e17092

Remove default parameters

b23cd26

AnirudhBhat requested a review from kidinov December 6, 2024 10:52

kidinov reviewed Dec 6, 2024

View reviewed changes

AnirudhBhat added 8 commits December 9, 2024 09:08

Remove unnecessary methods

f1f54b0

Remove unnecessary mutex lock

dfaa6fe

Use load more job to show pagination state

ead136f

Add test to verify we show pagination state loading when updating vie…

a2f171c

…w state if load more job is active

Add test to verify we show pagination state None when updating view s…

402e9e6

…tate if load more job is not active

Fix detekt error

0fb909e

Handle pagination state for remote fetch

37060cc

AnirudhBhat requested a review from kidinov December 9, 2024 05:33

Add additional condition to determine whether to load more or not in …

bd39579

…the variations screen.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[WooPos][Non Simple Product types] Retry UI for pagination errors on variations screens #12972

[WooPos][Non Simple Product types] Retry UI for pagination errors on variations screens #12972

AnirudhBhat commented Nov 21, 2024 •

edited

Loading

dangermattic commented Nov 21, 2024 •

edited

Loading

wpmobilebot commented Nov 21, 2024 •

edited

Loading

wpmobilebot commented Nov 21, 2024 •

edited

Loading

codecov-commenter commented Nov 21, 2024 •

edited

Loading

kidinov commented Nov 21, 2024 •

edited

Loading

AnirudhBhat commented Nov 22, 2024

malinajirka commented Nov 22, 2024 •

edited

Loading

kidinov commented Nov 22, 2024 •

edited

Loading

kidinov Nov 22, 2024 •

edited

Loading

AnirudhBhat Nov 26, 2024

kidinov Nov 22, 2024 •

edited

Loading

AnirudhBhat Nov 26, 2024

kidinov Nov 22, 2024

AnirudhBhat Nov 26, 2024

kidinov Nov 22, 2024

kidinov Nov 22, 2024

AnirudhBhat Nov 26, 2024

kidinov Dec 5, 2024

AnirudhBhat Dec 6, 2024

kidinov commented Dec 5, 2024 •

edited

Loading

kidinov Dec 5, 2024

AnirudhBhat Dec 6, 2024

AnirudhBhat commented Dec 6, 2024

kidinov Dec 6, 2024

AnirudhBhat Dec 9, 2024

kidinov Dec 6, 2024

AnirudhBhat Dec 9, 2024

kidinov commented Dec 6, 2024 •

edited

Loading

AnirudhBhat commented Dec 9, 2024

kidinov commented Dec 9, 2024

AnirudhBhat commented Dec 10, 2024

kidinov commented Dec 11, 2024

[WooPos][Non Simple Product types] Retry UI for pagination errors on variations screens #12972

Are you sure you want to change the base?

[WooPos][Non Simple Product types] Retry UI for pagination errors on variations screens #12972

Conversation

AnirudhBhat commented Nov 21, 2024 • edited Loading

Description

Design

Implementation

Testing information

Retry pagination UI

Navigate to items list after payment success

Changes to messages

The tests that have been performed

Images/gif

Reviewer (or Author, in the case of optional code reviews):

dangermattic commented Nov 21, 2024 • edited Loading

wpmobilebot commented Nov 21, 2024 • edited Loading

wpmobilebot commented Nov 21, 2024 • edited Loading

codecov-commenter commented Nov 21, 2024 • edited Loading

Codecov Report

kidinov commented Nov 21, 2024 • edited Loading

AnirudhBhat commented Nov 22, 2024

malinajirka commented Nov 22, 2024 • edited Loading

kidinov commented Nov 22, 2024 • edited Loading

kidinov Nov 22, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kidinov Nov 22, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kidinov commented Dec 5, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AnirudhBhat commented Dec 6, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kidinov commented Dec 6, 2024 • edited Loading

AnirudhBhat commented Dec 9, 2024

kidinov commented Dec 9, 2024

AnirudhBhat commented Dec 10, 2024

kidinov commented Dec 11, 2024

AnirudhBhat commented Nov 21, 2024 •

edited

Loading

dangermattic commented Nov 21, 2024 •

edited

Loading

wpmobilebot commented Nov 21, 2024 •

edited

Loading

wpmobilebot commented Nov 21, 2024 •

edited

Loading

codecov-commenter commented Nov 21, 2024 •

edited

Loading

kidinov commented Nov 21, 2024 •

edited

Loading

malinajirka commented Nov 22, 2024 •

edited

Loading

kidinov commented Nov 22, 2024 •

edited

Loading

kidinov Nov 22, 2024 •

edited

Loading

kidinov Nov 22, 2024 •

edited

Loading

kidinov commented Dec 5, 2024 •

edited

Loading

kidinov commented Dec 6, 2024 •

edited

Loading