[Design Issue] Explore expansion from one APD focus to Application focus

[beparticular]

Note to self from a discussion - if it's not a linear process, why is it a linear form?

TBD, but for grooming to be on the board - Thinking about whether lock and submit, export, error check, create new APD all live outside the actual APD form.

As part of this - we need to determine where the error check starts. Is it the export and submit page, or the dashboard or the side nav. Does it live with the export or submit? Does submit continue to exist? Do we need an export button and an "export to submit" button? This grows beyond the error check designs and into the lockdown and submit area, so it might not be right for this issue. Perhaps this issue can focus solely on what happens after the check is started.

Does the nav bar on the side need to change from presenting a form to presenting more like a web app?

There are many considerations for how we do this expansion.

---

Link or add dependencies to any applicable issues.

Include an explanation of why the design was created or changed, any decisions or conversations that led to this design, any regulatory notations, any user needs that should be surfaced, any risks, or what the user should be able to accomplish once this is done (as appropriate for the particular design).

Include any links or relevant information from Slack conversations that are related to this issue.

Add any deliverables like a mockup, or a link to a prototype, a link to a Figma file etc

Add in screenshots or annotated screenshots that show context of the request within the app, or show before and after if appropriate, however it helps to illustrate a concept or request

If needed, a note about priority (future enhancement tag, before initial release, etc)

This task is done when…

• [ ] any acceptance criteria (not process oriented, requirements of feature)
• [ ] designs are created, taking into consideration validation, multiple FFY, multiple entries, long entries, weird entries, and/or the export view if applicable
• [ ] 508 considerations and/or recommendations are reviewed
• [ ] designs are shared
• [ ] designs are approved by product
• [ ] if there is a long discussion, a summary of changes for dev will be added to the last comment before transfer
• [ ] a list of changes to be made if this is improving an existing feature

---

Add additional labels (design, dev, compliance, BUG, etc) and size before submitting.

If the issue is needed to complete prioritized work for the CURRENT SPRINT, add it to the "This Sprint" pipeline. Otherwise, all other issues will be automatically added to the unprioritized pipeline for prioritization in backlog refinement or sprint planning with Product.