Add Beta Issues

[josemvidal]

Add all the features you will implement for Beta as Issues and associate them to the Beta Milestone.

When you are done, close this Issue. I will then check your Beta Issues and tell you if I approve them or not.

Also, remember to Watch the 492Spring2024 discussions repo in case we post announcements.

[jbytes1027]

@josemvidal Issues added.

[josemvidal]

Beta features look good, they are Approved: #44 #51 #57 #61 #64 #67 #155 #156 #157 #201 #204 #213 #214 #215 #216 #217 #218 #219 #220 #221 #222 #223 #224 #225 #226 #227 #228 #229 #230 #231

Does this webapp use any third-party APIs? access data from other servers?

Does it do any sort of data manipulation?

From what I can see, all the features are basically CRUD Text data from the user. Note that an A-level app for this class needs to do a bit more than just CRUDing text (good enough for a B-level app).

[jbytes1027]

Hmmm. Will discuss with team. You're very right; our product is not much more than text manipulation on purpose. I've been trying not to design any complicated features and instead focusing on what I thought was important. This is the first time I'm hearing that we need a level of technical sophistication to our product beyond it being a web app with a custom backend and testing. Consider adding this to the course learning outcomes and 1.0 release for what makes an A-level app. I got the impression that professionalism and functional completeness is what you were (pretty much only) grading on.

In general, our product being a web app makes it complex in nature even if it is more or less text manipulation as it requires managing a frontend, backend, deployment service, and testing. This implies frontend state management, authentication, testing libraries, UI libraries, and basic styling. We don't have any less coding or learning to do than a more technical product idea.

[josemvidal]

See https://capstone.cse.sc.edu/milestone/release1.0/#grading-rubric

I like to see webapps do more than regular CRUD stuff for a solid A. Once you CRUD one table, all other tables are just more of the same.

Of course, a solid CRUD app will get a solid B.

[jbytes1027]

Ok, we will see what we can do: revised beta issues may be incoming. Consider adding more to the rubric as I'm not quite getting from it the same things you are.

[evan-scales]

Our chat feature uses signalR to add real time communication. Does that make our app more than just "cruding" text? @josemvidal

[josemvidal]

If this SignalR then yes, that is a third-party API (even if, technically, still Microsoft)

[evan-scales]

Yep, that's exactly what we use. Would that alone still allow for an A-level app? Or would we need more?

[josemvidal]

Yeah, that seems like an A-level feature set.