About collection-repeat and filters on tinder-cards

[lmoncany]

Nice to meet you all, I'm loic, a french guy working on a wonderfull ridesharing app built with ionic and rails. I'm here for taking advices,

I use ionic-ion-tinder-cards to display trips on a search results. It's working but i would like your advices about the method to work with filters and tinder cards. There will be a lot of cards... and a lot of filters, they will be filtered first by the origin & destination city searched and after by a filter modal.

Questions :

1 - ng-repeat or collection-repeat ?

2 - filters on back-end or on front-end with angular filters ?

3 - any other advice to do it ?

Thank you !! ionic rocks !

[lmoncany]

Up

[ihadeed]

Hey,

Just looked at your issue really quick.

Your app looks nice!

I'm not sure what would work out better (ng-repeat vs collection-repeat)
but what works the best for me is ng-repeat with a tracker (track by id or
track by $index). That mininizes DOM changes in the long run.

As for the filtering, it depends on when is the user supposed to apply the
filters, what kind of filters, and how fast do you need to get back to them
with the results. I will give you two scenarios where I personally pick
backend filtering vs angular filtering.

1. I have a page in an app that shows you a list of your friends. It's a
   small app, users don't have many friends and they can all be loaded at the
   same time. Now I would like to implement a search feature so you can type
   in a few letters to filter the friends list and find a specific person. I
   use angular filter in this situation because: I already have the data
   loaded up, I will need to reuse all the data later on, and the user is
   expecting immediate results when they start typing in that search box.
2. I have an application like yours for ride sharing. Users are supposed to
   supply me with information before hand (from location, to location,
   departure time... Etc) for me to find a match or a few matches for them. In
   this case I would set the search form to be in a separate page and every
   time I update that information and it gets sent to the sever for
   processing. I let the server handle it because it's much easier to run
   these kind of queries there. You might need to do some Geolocation based
   calculations or perhaps filter thousands of database entries.

So to sum it all up, if you need to filter big data it's better to do it on
the back end for two reasons:

• you don't need to let the user download data they dont need
• servers are more powerful than smart phones and they are able to apply
  multiple filters faster. Most of the filtering can be done in the database
  query.

I hope that helped!
On May 9, 2016 10:44 AM, "lmoncany" notifications@github.com wrote:

Reopened #87
#87.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#87 (comment)