JavaScript is required to use Bungie.net

Companion App

What needs work in the Companion App?
11/11/2019 1:10:57 AM
1

About LFG section of app.

First, and the main reason for the post, is that we need either a "body" section to add details for specific teams comps, strats, loadouts, or whatever a player might be trying to do in whatever way. Either that or increasing character limit from 50 to 75 or so but the latter would be a nicer addition imo. Also while I'm thinking about it, I understand why something is set up to limit people from spamming messages but I think it could be implemented differently. First you can't message a person privately more than 2 or 3 times before you have to wait. This includes messaging one person and then quickly sending someone else (who joined group) a different message. What I find most odd is that while there are restrictions on message frequency, there isn't any limit on spamming lfg posts. Actuary you can spam lfg posts pretty much infinitely (which is the real problem due to carry/recovery scammers). It's just kind of backwards IMHO. Honesty I'm just psyched you can invite people from the app. We've come a long way since the dark days of Destiny 1. Though I must say the GamerLink app has much more optimized lfg app for getting specific details across when attempting to put together specific team comps. But it is specifically an lfg app. Anyway, just a couple ideas. If you made it this far, thank you for taking the time.
English
#companionapp

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • There's enough room to put some basic details in the Fireteam name, and you can hammer anything else out in chat or messages. Are you hoping to add an encounter-by-encounter walkthrough in the app before inviting someone?

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon