Matchpool - Making Human Connections updated info



  • Matchpool Development Update - FEATURE ADDITIONS, BUG FIXES & More




    Report — November 1st

    This week, our development team focused on improving the matchmaking experience by allowing users to send greeting messages to their requested matches. Though this is a small feature addition, it will enable users to make a great first impression when reaching out to potential matches, engage in better communication and drive success in their matchmaking endeavours. The team also worked to resolve several platform bugs, including: bugs related to saving profile information and, issues with fee payments & join request list updates.

    FEATURE ADDITIONS

    1. User-requested matchmaking

    Pool members no longer need to hope they’ll be matched;, they can now go ahead and send a greeting message to their desired matchee. This feature will allow users to make a great first impression on potential matches and significantly bolster their chances of securing their perfect match.

    Next week, we’ll be featuring the Greeting Message feature in our weekly highlight series.

    BUG FIXES

    Profile image error — The team mitigated a bug that some Matchpool users were experiencing when saving their profile information.

    General bug fixes — The team worked to resolve several small-scale bugs on the platform including:

    1. An issue with the join request count updating correctly. It wasn’t — but now it is.
    2. The ability for users’ avatars to be correctly displayed in public chats.
    3. Minor issues when paying messing pinning and direct message fees.

    Upcoming Features

    Next week, the team will be focused on implementing a feature that will allow users to re-use the same Ethereum address across several Matchpool accounts. Users will be able to have several Matchpool accounts, without having to tediously create new Ethereum wallets for each individual account.

    Conclusion

    Matchmaking is the core of Matchpool’s ecosystem. By allowing users to send a greeting message to potential matches, users can increase their chances of securing a successful match. Several bugs, such as those plaguing the: join request count, profile information saving feature and fee payment process were also resolved, allowing for a more refined and professional matchmaking experience. If you have feedback about these new features, or about your Matchpool experience in general, please join our Telegram and let us know what you think. All feedback is appreciated.

    Thanks for reading and match on!

    Yours,

    The Matchpool Team.




  • Weekly Feature Update: Swatting Some Bugs!

    Matchpool Development Update 11/11–17/11

    Overview

    This week, we’ve began pursuing the goals outlined in our Winter Roadmap. The focus for this week was to remove several small-scale bugs that persist on both the Android app and web platform. A functional, bug-free platform is crucial for an enjoyable user experience. With the bug fixes and performance improvements made this week, users on both our web platform and Android app will have a more enjoyable matchmaking experience.





    Android application

    Bug fixes and performance improvements

    One of the goals of our new Roadmap was to give our Android app extra developer attention and resources. This week, we’ve focused on the removal of annoying bugs that have been persistent on the Android app. Specifically, we’ve taken aim at bugs related to intro requests and general app stability. We’ve also taken time to to focus more intensely on improving paid pools. Below are some key improvements we’ve made to our Android app:

    1. Often, when a user joins a paid pool, the “Join Pool” button would still be unnecessarily displayed. This bug has been resolved.
    2. Pool admins were at times, unable to set a custom join fee. This bug has been resolved.
    3. “Interests” tags could not be edited by users. This bug has been resolved.
    4. After updating the app, the user must logout and log back in. This bug has been resolved.

    Note: The above changes will be applied to our Android app at the beginning of next week (Starting November 18th.)

    Web platform

    Bug fixes and performance improvements

    This week, bugs related to intro requests were the primary focus of the development team. Below are some key improvements we’ve made to our web platform:

    1. Members and pool admins weren’t receiving proper notifications regarding user matches. This bug has been resolved.
    2. Members requesting matches would still unnecessarily see the “Request Match” button for users that they’ve already request a introduction with. This bug has been resolved.

    Conclusion

    Our team has spent the week focused on mitigating several bugs on both the Android app and web platform. These bugs have affected intro-requests, paid pools and pool admin customization options. The mitigation of these bugs and the general improvements made this week will give users a more enjoyable matchmaking experience.

    What’s next?

    Next week, our team will focus on removing bugs pertaining to private chat and messaging on both our web platform and Android application. Stay tuned for more news and updates from the Matchpool team!

    Check out our official applications!

    Thanks for reading and match on!

    Yours,

    The Matchpool Team.




  • Matchpool Development Roadmap

    Matchpool’s Official Development Direction for Q1 of 2019

    Overview

    Greetings community and happy New Year! We’re happy to release our development roadmap for the first quarter of 2019. During this phase of development, our team will work on adding new features to our platform. These features will: allow pool admins to suggest matches, allow users to post bounty requests, enable matches to be made outside of pools and include the implementation of a new matching type. The team will also resolve several bugs and markedly improve the platform’s UI, giving users a more clean and immersive matchmaking experience. Overall, Q1 of 2019 will be a busy time for us. We’re delighted to be delivering new tools and improvements to our platform and enhance the user experience.

    Phase 1 — January 1st — 31st

    Target: Web application and Android application

    Continues work on the new feed UI a. Add an automatic unpin messages mechanism. b. Enable pool members to direct message the pool admin for a fee and vice versa. c. Allow pool members to post and comment using images. d. Brand new design for the pool’s “About” page. e. Brand new design for the pool member profile page.

    Phase 2 — February 1st — 21st

    Target: Android App

    Allow users to pay what they want for a match a. Change the request process to include new parameters. b. Change the request display to admin which includes new parameters. c. Add a rejection option users can employ if the suggested amount of Guppies is deemed too low.  d. Add a new page for admins — through which admins can view all pool match requests. e. Add a new page for users — through which users can view all of their match requests.

    Phase 3 — February 21st — March 11th

    Target: Android App

    Allow users to request a match from any pool member

    a. Change the “View all match requests” page to enable visibility by all the pool members. b. Change the approve/reject match process so every pool member can accept desirable matches (note, only the pool admin can reject matches.)

    i. The request will be posted on the “pool matches marketplace.” ii. User C will only be able to match User A (requesting) with User B (requested) if User C is already matched with User B. iii. When user C approves the match request, User B will be able to approve or reject it. If User B approves, the request is send back to User A for final approval and payment completion.

    c. Filters will be added to the “pool match requests marketplace” and “my match requests” section.

    d. Once someone replies to a match request, the request will be locked, preventing other users from responding to it until User A decides to reject the match.

    e. User B will be able to play the role of User C and suggest himself as a match. In that case, the pool admin will collect the bounty.

    Phase 4 — March 11th — 25th

    Target: Android App

    Allow users to post bounty requests

    a. Create a new match request type.  i. Allow members to request to meet other members who match certain criteria, including:

    1. Title

    2. Text  3. Must-have tags  4. Nice-to-have tags

    b. Create a new page where users can view their “match requests” i. Display the original request. ii. Display all the suggestions users received for the bounty. iii. Allow the user to accept or reject each suggestion.

    Phase 5 — March 25th — April 11th

    Target: Android App

    Allow matches to be made outside of your pool.

    1. Allow pool admin(s) to suggest matches from other pools he is a member of.

    i. The match will be successful if User B joins the pool User A posted the bounty on.

    2. Allow pool members to suggest matches from pools they admin.

    i. The match will be successful if User A joins the pool User C admins.

    Conclusion

    We’re eager to embark upon our next phase of product development. Over the course of this development schedule, our platform will be packed with many new features, UI improvements and bug fixes. We’re eager to deploy these new and exciting changes to our apps and look forward to the community’s feedback and comments. Be sure to join our Telegram to stay up-to-date on all of the latest news and announcements from our team.

    Check out our suite of applications!

    Thanks for reading and match on!

    Yours, The Matchpool team.



Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.