Comments on 1-overview.md left as HTML comments in raw source. Any...
Compare changes
+ 15
− 0
@@ -12,3 +12,18 @@ No question is asked more in the comic book community. I have chosen this app as
Marvel comics, especially _Daredevil_, are books that I take great joy in reading, but it gets tedious when figuring out the reading order. Having this app to neatly exhibit all the comics in each storyline, trace my progress and visualise how far I have to go will be invaluable. The comic industry is notorious for being difficult to follow as its characters have been getting consistant books since as early as the 1930s, 1964 in the case of Daredevil.
This is a really interesting idea, one that I think permits a good level of challenge in terms of presentation (i.e., UI) and data structures (i.e., how this will be stored and represented interally). You have clearly defined a use case and audience. I have a few things for you to consider as you work on the project.
1. We do have scholarship marks available to recognise additional efforts, but these need to be related to the development of the artefact. It might be useful to limit yourself to creating a comic map for a few example issues, just to prove the concept. Spending a lot of time doing the labour of inputting information for dozens and dozens of these would certainly be a good contribution to the commuinity... but not so so easy for us to give you marks for!
2. Make sure you are thinking about ways you can leverage the Android API (including through your own Scholarship) to really demonstrate the depth of your skill. You don't want anything to feel crowbarred in, but at the same time, you need to be able to demonstrate that depth. It's not immediately apparent how you will do that from the overview. Perhaps you could give a somewhat clearer picture of the features you indent to include (appreciate you're already at the word count...)? It's not technical at all, that goes in other sections, but just a bit of signposting so that someone who read the overview would be able to form some expectations about what the app will do before they open it.
3. Data modelling is going to be important here! You have a number of nodes which will have a variety of relationships with other nodes. Think carefully about the different options available (e.g., DataStore Proto, Room, Firebase etc), and work out which one is going to fit best for the kind of modelling and representations you're going to need for this application.