Support Contact Form: Main Issue

This issue centralizes all tasks and potential improvements to the Support Contact Form implementation on WPAndroid.

To Do

• Introduce basic implementation (PR: #15349)
• Review the form screen design.
  • Decide which fields we want to include.
  • The site picker should probably show the site's icon and URL.
  • The progress bar should be consistent with what we have on other screens.
  • The form screen layout should be optimized for landscape orientation.
  • Handle the scenario where the user doesn't have any sites.
  • Investigate why line breaks don't render consistently in the chat screen when compared to Zendesk on the web.
  • Consider when we want to show the form screen (should we replace all existing entry points to the chat screen?).
• Add tracking.
• Review current architecture.
  • SupportFormViewModel is not currently being used, which makes the form screen behavior hard to test.
  • We should also consider making some of the logic inside ZendeskHelper more testable.
• Add tests.
• Add documentation.
• Consider using UploadProvider to add a way for the user to attach files to the request.
• Consider handling other scenarios.
  • We can refer to Calypso's HelpContact for some examples.
• Consider moving existing classes (HelpActivity, ZendeskHelper, and SupportHelper) to the same package.
• Consider renaming new and/or existing classes for consistency.
  • We should at least settle into a single prefix like Help or Support.

Notes

• Please check this internal ref for more info: pbArwn-2Wq-p2

Start by reviewing PR #15349 and the existing Support Contact Form implementation, including SupportFormViewModel, ZendeskHelper, HelpActivity, and SupportHelper. Use the checklist to determine the intended scope; completion would require settling the design, architecture, tracking, tests, documentation, and additional scenarios listed here.