Evgeny Zaritovskiy
My feedback
561 results found
-
41 votes
An error occurred while saving the comment -
5 votesEvgeny Zaritovskiy
responded
Current Wild Apricot position on Public roadmap:
- our current Roadmap is what we are working on now – https://forums.wildapricot.com/forums/308932/status/1547997
Our “Work in progress” list can take us easily up to year to complete and we constantly updating it. Whoever voted for an idea, will automatically receive updates when we update its status- we used to publish our roadmap but цуку never able to fully follow it and it always produced tensions from customers following it; the roadmap was always perceived as a a promise even though we kept repeating it was not
- publishing roadmap requires some place to discuss it; people have different priorities, arguments happen, this all need ongoing moderation = time. We have no special place for it, except this forum – and its already serving this purpose.
- we use Voting system here to inform us on our customers priorities (the more votes, the…
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Walt, we're considering having one mire status similar (or even the same) as you suggested. Thanks for comments, appreciate it
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Original comments posted at https://forums.wildapricot.com/forums/308932/suggestions/12479814, but removed as not related to the discussion and posted here.
===
Robin commented September 23, 2018 3:35 PM@evgeny zaritovsky
While fully understanding the process in the software development world (I have been involved in that for more years than I care to remember) and that there are only so many resources (people, time and money), it is also important that the enhancements being developed are what the customer want the most and not what the architect thinks are the coolest. And with all due respect to the architect (and I have often seen this), the architect does not use the software every day to support the needs of the customers and sadly is often out of touch with these needs.
Now obviously, I am going to consider some requirements as more important than others and vice versa.
But we 'the user group' of WA really have very little idea of what is in the pipeline and how it is going to be implemented until it is announced as delivered in the latest release.
Your team on the other hand as per your post below, do have a plan. And I understand that it is only a plan and that it may not actually be delivered.
I would however strongly suggest that to be fair to your current customer base, that you publish your tentative development plan of what WA is considering of delivering in the next 12 and 24 months and additionally of any other items in the wishlist if they are still possibly being considered for future delivery or are totally off the list.
Collectively, we the WA customers give WA a very large amount of $$$ every year and as most of us are not for profits - these $$$ are really very expensive for us, even more so for those of us from outside of the USA who also have to face exchange rates.
Are you legally obliged to tell us what you are thinking of delivering? NO. Is it the ethical thing to do? YES.
If you publish this list as a forum item and make sure that you inform ALL users of its existence, you will most certainly get a whole lot of feedback as to what is in the pipeline. It will either verify that what you are planning is what the users want to tell you that you have it totally wrong. Either way - it would be good feedback and if responded to would significantly help to grow your customer base and maybe even more importantly retain your existing customer base. Keeping existing customers is much more cost effective than acquiring new customers to replace those who have left. And while maybe not in these forums, but in the WA Tribe FB page I see way too many comments from people who are saying that lack of certain features are making them look at other platforms.
=====
Walt Bilofsky commented September 24, 2018 10:12 AM@Robin: +1
What portion of the WA user base actually participates in the Wishlist? How many of us who do are aware of all the possible enhancements being discussed?
My guess is that we are not a good sample, and not very representative because those of us here are either more interested in the systems, more power users, more unhappy with something missing, or a combination.
If WA is interested in aligning development with what the user base wants, Robin's suggestion to inform ALL users of the roadmap is a good way to do it.
I will also suggest that from a marketing point of view, one way to build loyalty among customers is to instill a sense that the vendor is listening to them (without, of course, raising unreasonable expectations).
=====
Robin commented September 24, 2018 12:55 PM@Walt, well stated.
The methodology of informing customers has many possibilities. The key thing is to actually inform customers of what is in the 12 month and 24 month pipeline (planned and may not be delivered) and to also provide details before implementation as to how it will be implemented so that customers can provide feedback on proposed solutions before they are set in concrete.
=====
Walt Bilofsky commented September 25, 2018 12:59 AMI think the developers do a pretty good job of providing details to this group before implementation of complex features.
What is needed from the broader customer base is prioritization of features. So bring back the public roadmap, and be clear on functionality, but not necessarily design details.
=====
Evgeny Zaritovskiy (Product Manager, Wild Apricot by Personify) commentedWalt, Robin, I believe the this Wishlist forum is exactly the tools for the vendor (us, Wild Apricot) to connect and listen to our customers (you). We - I as Product Manager, and all our Product owners, responsible for particular areas of the product - are receiving every comment and new idea posted here. This is basically how my day starts - reviewing all the feedback. So on this regard, I believe we're doing a good job and so far I have no plans to change it.
As for public roadmap: we use the voting system in the Wishlist to guide us on priorities if our customers.
Evgeny Zaritovskiy
shared this idea
·
-
255 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
@Walt, Robin - I have deleted your comments on Public roadmap from here and moved them to a separate new thread.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
No updates so far. This is less about difficulty, more about our priorities - we focus on other things now. We have it in our list of candidates for next year, but it does not mean we will actually implement it.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Hi D Lee, not sure if I understand you correctly. Admin with "Membership manager" access rights DOES have access to customize membership emails.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I merged the last 2 comments into this thread (Custom permissions) as this is currently seeing as the best approach to solve this and a lot of other related scenarios.
Evgeny Zaritovskiy
supported this idea
·
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I fully support , Liz. This is exactly how I was planning to resolve a number of accumulated various roles requests. Thanks for posting.
But we will have to keep in the wishlist for now. -
68 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Walt, storing credit card of members in Wild Apricot Payments (powered by Affinipay) is in our top list of features. But, as usual, not promises on particular release schedule.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
That's a very good and proper idea, the problem is that WA doesn't know anything about billing address of your member: all member profile fields are same and there is no (easy) way to extract billing related details from them. To address this properly, we will have to implement something like special system field for billing details or have some kind of mapping page for payments, where admin can map member profile fields to billing fields on credit card payment page.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
That was the first thought in my mind too but I'm kind of reluctant to add one more setting screen (especially with fields mapping) - it's too technical and complicated to understand in general.
Though thanks for the comments.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
It's a good point, thank you. Actually, we just introduced the ability to charge CC through WA and we agree that it's not ideal yet. We implemented fast and easy solution - give administrator same interface as for member.
Your suggestion is very logical but the problem is in fields mapping - to make pre-population possible, we have to find a way to map your contact database fields to credit card screen fields. Unfortunately, it's almost not possible to make it automatically - Wild Apricot (as a system) does not know which of your fields are address fields (they can be named differently). There are different ways of resolving this problem, we will consider them as soon as we can (not soon, sorry).
Or may be I'm missing something obvious here and somebody can suggest quick and easy idea for automatic mapping?
-
74 votesEvgeny Zaritovskiy
responded
Merged several posts together, so that both public and admins lists can be customized. This is better for analysis and design to work on them together.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
No updates so far
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I think the better way to solve this is to actually implement RSVP feature.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Merged with similar one.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Sure - moved your topic and renamed it too. I assume that the general idea it to be able to customize what should be shown on the public event attendee list.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
It is in wishlist, let's see what others say about this
-
123 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Not in immediate plans so far.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
You can pay for 2 years with 15% discount starting form after April 3rd.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
We're not planning to change our pricing model soon, but I'll keep the requests here so other people can comment as well.
-
225 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Nothing to comment so far, this is in the wishlist. As soon as we take it into works, we will post an update here.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Everything we're working on now and our nearest plans are presented on our Roadmap
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Thanks for the comment. I'll take this into consideration when we are at the design stage - but this is still some time ahead.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Hi skipat - sorry for a late reply!
Is it enough to send e-mail to all event attendees (similar to reminder) or you need a way to select specific group within attendees? If we are talking about specific group within attendees, do you have any idea how would you define such a group?
-
170 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
(Walt - thanks)
Robin - if something is in wishlist, then it's just waiting its turn to get attention from a product management team (me and smoother folks). So far, this has been postponed; no further details that I can provide, including forecasts.
Re "post a WA response within say a week", "For all open wishes – post a status update say every month or 3 weeks". Personally, I see no point in saying same thing over and over again - "this is not in our plans and I have details on future plans". As soon as something gets into analysis, we change status in "Work in progress" and this is the biggest notification we can make.We're monitoring all the comments for all threads, but not always comment back. Most of comments just add more details into existing items and this helps us with prioritization for the future. Basically, more votes - higher chances for it to be prioritized, but this is not promised, as we have internal business plans as well and a lot of background activities that require resources.
Frankly, I believe with the number of overall suggestions on the wishlist, we're doing pretty good: we collect feedback, we make reasonable progress with it, we communicate. Can be better, I agree, but overall I feel quite good on how we manage the forum here.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
This is not yet something we’re looking into.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Sorry, Lucy, no ETA yet. This was in the roadmap, but things have changed. This still in our short list, but I cannot promise dates.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
1 and 2 is in the solution design we prepared, #3 is not going to be covered here for now.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I understand your frustration, but we have a limited number of resources and majority of them are focused now on the next 5.0 release - see http://www.wildapricot.com/blogs/newsblog/2013/08/28/wild-apricot-software-news-august-2013
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Just a typo - I meant "in our queue" - which means we are aware of this but it's not in development yet.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
This is still in our queue and no chance it fits in 2011
-
52 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
No in development plans for now
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Unfortunately this is not going to fit into 2011
-
7 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Just to clarify: are you talking about self-service account cancellation feature as described in this help article - http://gethelp.wildapricot.com/en/articles/53 ?
-
90 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Good idea, thanks for sharing. Is anyone else interested in this kind of enhancement?
-
240 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Gerald, I hear you on this one. The problem is that our priorities and roadmap is already compiled and being worked on, we cannot really add something into next release.
On a positive side, our events development team is monitoring comments like this ones and if we believe that we have to change our current priorities, we will.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Liza, we understand the importance of this feature and I totally agree that it is very useful for word of mouth scenarios. Unfortunately, it is not in our nearest plans. We will update this post as soon as we start working in it.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I'm sorry to hear this, Scott - but it is what it is. Current system does work for someone, but I agree it is not the best and very inconvenient. We're listening and currently focusing on highly requested suggestions, but this one is still not in focus.
Evgeny Zaritovskiy
supported this idea
·
An error occurred while saving the comment Evgeny Zaritovskiy
commented
We do read, but this is not something we're working on right now. As soon as there is something new to share, we will post it here right away.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Can registration types with code help?
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I can answer on behalf of her - no, unfortunately. It's almost impossible to guess actual timeline for any feature as it depends on too many other things. We used to try and almost always missed it do we decided not to do this anymore.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Not in 2013, sorry - but we are currently performing analysis and design.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Again, why not creating a single registration option (with reduced price) that requires code to use (this is possible to do in WA)? You can email the code to 500 people with instructions to use specific registration option and enter the code during registration.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Sorry, no plans yet. Why hidden registration types do not work for you? Or you want to suggest registration without actually showing any price until code is entered?
An error occurred while saving the comment Evgeny Zaritovskiy
commented
That makes sense, thank you for more details. What if instead of having 3 registration types for 1, 2 or 3 day rates you create it as "extra-cost" with 3 radiooptions? This would reduce total number of reg types to 4.
And I also think if we make a change in the system and allow to have "extra-cost" value to be negative, can it work as discount? In your case there could be additional "extra-cost" checkbox like "I'm student" which gives a certain amount of discount.
I would be glad to hear your comments.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I believe that this particular situation can be resolved by just creating a separate registration type on event with reduced price. No need in special discount coupons.
-
90 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Scott, thanks for sharing and was nice meeting you at the PersoniFest!
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Thanks for mentioning it here - we already have this comment in out internal database of ideas but not here.
-
85 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Ho Donna, there have been no progress on this particular request and it's not in our radar so far and can make no promises on dates (as with any other feature).
An error occurred while saving the comment Evgeny Zaritovskiy
commented
For now, we simply count how many people commented in a specific wishlist thread. The more authors a thread has, they higher is its priority.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Thanks for sharing the details. This is still in queue, but when we are ready to proceed with it, we will be using your information in our analysis.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
No, not done yet - this is why it's still in Wishlist forum.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Thanks for your comments, Nick, but you'll have to make your decision on what Wild Apricot currently does, not what it may suggest in future. We cannot promise any timeline for any new feature, it depends on too many conditions and missed our plans many times, so you cannot rely on that in your decision making.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Can you please provide more details? For example, how would it work in your particular organization. This would help us in our analysis.
-
51 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Robin, let me answer as a Product Manager of Wild Apricot.
First of all,
thank you for being active contributor into Wishlist forum. I can see that you have supported over 100 ideas for several last years. I (and all of us in Wild Apricot) appreciate feedback form customers as this helps us in further product planning, analysis and design.Secondly,
I understand your position. Everyone wants (including me) to have their ideas implanted as fast as possible, not after several years. I wish we can do this, but goes to the next point.Thirdly,
Wishlist forum has over 2000 open ideas in the Wishlist forum (and over 30K users) and this particular one has (only) 25 votes. Why I say "only"? We have about 200 other ideas with more votes than this particular one. We need to prioritize somehow. Number of votes is on of the key metrics in the prioritization - but not the only one, see next point.Fourthly,
Wishlist is a great source of customer feedback, but this is not the only source of our product prioritization. We have our own business plans (e.g. business growth), other feedback channels (e.g. Support), security requirements (e.g. PCI DSS, GDPR), infrastructure works (hosting, code deployments, performance), decreasing tech debt (refactoring of code) and so on. All these requires some kind of balance and resource planning. We are paying attention to Wishlist and user votes contribute a lot into prioritization, but not just it.Fifthly,
I looked into suggestions that you voted for over time and I can see that we have closed a number of them over time - which means we are working on it. For example:
- Prioritize Test Emails Ahead of "Final" Email Blasts
- Allow secondary/alternate emails for members
- Restricted access to documents and images (member only files)
- Registrant to view and change his event registrations
- RSVP - Simplified event registration
- Generating membership cards and certificates
Some more are in progress right now:
- Membership Trends Reporting
- Polls
- Uploading documents and photos in forum and blog posts
- Mapping location of members
Altogether, last year we closed about 1500 of votes on the wishlist (mostly top voted requests). We're paying attention to the forum and making progress over it.Sixthly,
we do not share dates on purpose. Long time ago we were promising some releases dates but our expectations were always breaking. Situation changes all the time - people come and go, development can stuck at some unforeseen issues, a feature takes longer than expected and we see other opportunities. There is a lot of operational hidden activities that influence the end results that we decided not to promise at all.
My (our) position is simple: Wild Apricot is what it is now and it provides what it provides. We are committed to improve it over time, but this is a bonus, an extra thing. We won't be promising any dates and won't commit to anything. Instead, we openly share where we are and if we started working on something, we change status as "Work in progress" and it tells the world that at some point we may release it. "May" because situation can change and it can go back to backlog (postponed).So, in short, this is not something we're going to have in 2018.
Robin, I do no want to seem rude and forgive me if I sound like one. As I said, I appreciate your active contribution and we do have progress over ideas that you voted for. But product prioritization is a sophisticated thing and we cannot give any promises.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Sorry, we have no alternative solutions and this is not in our immediate plans so far, not for this year for sure.
-
221 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Making custom branding on App Store level is going to be a nightmare for Wild Apricot. It means that each app for each organization has to be published separately (uploaded, reviewed by App Store staff, enabled by WA). With our number of organization and number of employees, not worth of investments - until we charge some extra for it.
Branding inside the app, though, makes total sense for me and can be quite easily done.
-
120 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Because we have other things to prioritize, with more votes on them.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Would having a backup without possibility to restore it be interesting? Because importing a backup backup is much harder to implement.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Did you try to contact our support? We could have helped you to restore your content.
Re timeline: we were focusing on something else.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Sorry to hear about your accident. No, nothing changed in version 5 and we're not working on backup feature right now. See this thread about our plans and current progress - http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8827717-roadmap-2015-plans-releases-expected-dates
In this long discussion topic we've discussing what specifically people need from backup feature. Is it just
a) having a way to somehow download all the information in order to keep some copy on our own servers, but without restoring ability
b) or is it also about restoring, so you're not just backing up, but can restore from it too.
The difference is very big from implementation point of view. Doing A is much faster and easier, but has no real purpose except keep data on our computers and being able to manually open files and copy/paste data.
Option B is much more time consuming for us to design and develop.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I'll keep this in mind - we will update our procedures against aliens invasion (last time we hardly managed)
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Does it have any benefit, if there is only backup option (more like export - images, web content, etc.), but no import / restore back? The problem is that to have both is quite a substantial chunk of work and it's not clear yet when we're going to do something about this.
-
5 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Sorry, this forum is not about WA webinars
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I'm really sorry, but I cannot understand what you're specifically asking for. Integration between Wild Apricot and external system?
-
1 vote
An error occurred while saving the comment Evgeny Zaritovskiy
commented
I opened the post for commenting - may be some other developers will be willing to help and share the experience.
Sorry, I cannot help with instructions on now to setup streaming to members only. -
7 votes
An error occurred while saving the comment Evgeny Zaritovskiy
commented
Randall, thanks for your very elaborated thought on this matter. As of now, we have no plans to change our Web Content module that dramatically - this is going to be quite a big business enterprise. I'll share this with our CMS dev team so we keep thinking on how to improve and simplify our CMS, but I do not expect anything big to come our of this.
An error occurred while saving the comment Evgeny Zaritovskiy
commented
No, this is not in our plans, thanks for sharing your idea. Why do you think we should have it? Would be glad to get some details on the idea.
Walt, we did not do anything, all part of standard behaviour for years. No changes on our part.