Skip to content

Conversation

@joroSharp
Copy link

I decided to create a new Content Page that I will implement in the last version of my company app.

In the past, I created a similar view using ListViews, however, due to some problems with the performance of the animations in the Android version I decided to discard it and create a simpler version. I'm glad to see that thanks to the CollectionViews I've finally been able to create the view I wanted.

Screenshots

Android:
untitled

iOS:
2019-04-29_10-35-28-AM

What went well?

  • It is a very useful and flexible type of view thanks to its many customizable properties. Highlighting mainly the possibilities offered by ListItemsLayout.
  • It is easy to migrate a simple ListView into a CollectionView.
  • There is no reason to use ListView again.

What didn't go well?

  • It seems that there are some problems when assigning the size of the cells automatically. It is necessary to assign the size manually, however, this implies having to use different values according to the platform.
  • The way in which the selected color is assigned is poorly documented and unintuitive. In addition, all CollectionViews seem to read the same property, so there is no way to assign different selection colors to each CollectionViews.
  • There is no way to assign Transparent color to Selected Color.
  • When using ScrollTo with ScrollToPosition.Center in a horizontal CollectionView with SnapPointsAlignment="Center" sometimes fails and breaks the alignment.

How is the performance?

Better performance compared to a ListView, especially noticeable in the Android version. But the performance when working with animations in the cells can be improved for the Android version.

Missing or Desired Things:

I would like something similar to the OnAppearing event of the ViewCells for the DataTemplate.

Conclusions

I am very happy with the result of the CollectionViews. This is undoubtedly a really useful component that I will use in future projects, especially for simple lists. However, it currently presents some problems that I consider serious (such as size assignation) and that I really hope will be solved soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant