Aehmba {"ops":[{"insert":"1st It would be nice if I would be able to see in which decks my cards are just from looking at my collection. All that is needed is an option to show this as it was before the last big update.\n\n\n2nd It would be great if i could see how many cards i own from a specific card and how many of these cards are in which decks. We already have something like that, but split on to pages of the card info tap in the deck builder.\n\nFor example: I want to add a copy of Terminate to my deck and did so. Now i want to know how many cards of Terminate i own. So I click on the little arrow on the card to get to the info tap. Here i can view my collection on one page and what cards are in decks on an other one. Please give me one tap so i don't have to jump between these two.\n"}]}
1
{"ops":[{"insert":"Your first suggestion was removed due to performance concerns. Loading decks for every card on the collection page just isn't feasible at scale it turns out. We made the information as availible as we could through the use of the \"In Decks\" tabs on card details on the collection and deck pages, but that's about as far as we can go without slowing things down to a crawl. All the information is still there (and in the case of the deck page, it was added), it just must be requested per-card now.\n\nYour second suggestion, similarlly, it's built that way due to performance issues. Loading each of those tabs separately is a pretty costly operation. Loading them together even moreso. We chose to sacrifice a bit of UX to keep heavy requests to a minimum and keep the site running smoothly for everyone.\n\nIn a perfect world, I'd love to implment both of these suggestions. But unfortunately they're built the way they are to prevent slowdowns on the site. The thing you've gotta keep in mind is that while one person might be willing to sit there a little longer and wait for a request to come back, it's doing so at the cost of someone else having to wait. Do this too much or too often, and the site slows to a crawl for everyone. We've run into scaling issues in the past, so we try to avoid heavy operations whereever possible to prevent those issues moving forward.\n\nIf I do every figure out a way to do what you're suggesting without causing extra slowdows, I'll 100% do both though. What you're suggesting is the ideal operating behavior, but unfortunately concessions had to be made to keep things running smoothly.\n"}]}
1
{"ops":[{"insert":"Thank you very much for your replay. Now i understand why you chose to remove this. And thank you for the choice made. I, in fact, was a bit annoyed of the page often not able to load all card of a deck after opening it for the first time. This way it is way better. Thank you again for your detailed replay :)\n"}]}
2