Currently the audio receptive fields are not displayed well. Artifacts from removed graphs remain and the surviving graphs can be adjusted to more fully take up the user's screen.

Currently when audio is being processed, the UI pulls up the same page that it does for processing an image. This is confusing to the user since an audio recording is being processed, not an image. Change this so that it says processing sound.

The wording here seems really awkward to me. I’ll change it to “Now you can see the receptive fields generated from images and audio which match the ones generated in your brain!” unless anyone has anything else to add. I think this feels more natural. We’ll also need to explain what receptive fields are to new users first. See a below problem for something similar.

For new users, the homepage description won’t make much sense because outside of neuroscience, nobody knows what a neuron’s receptive field is. This will probably turn a lot of people off initially. When a user loads the app for the first time, I therefore think that they should automatically be shown the “About App” section which goes into more detail about the app, its purpose, and the underlying phenomena. They’ll have an option to skip it of course.

When viewing the recordings the user has made, the bottom part of the UI is unable to replay a recording as a normal person would expect it to. You have to reclick the same recording from the top part of the UI to replay it. We should add a replay functionality which replaces the triangular play button once the recording stops.

Fix grammar in description. "Looks" to "look" since "receptive fields" is plural

Currently, gammatone filters only display 8 graphs without axes or information describing what they represent. We need to 1, display data and plot the axes of each graph, and then include an information page to explain the purpose of both the gabor filters and gammatone filters and what they represent.

Currently, when you search for an app on the app screen, our app comes up with "Neuroscience" as the visible title and the stock default app icon there. We need to change this to something custom to our project.

I think that using the lab icon would be a good idea.

In my opinion, the button to process the audio into its corresponding receptive fields is not very clear, intuitive, or well positioned. I think that this may cause confusion for a small subset of users, so if anyone has an idea of how to make this more intuitive please tackle this one.

Add our names to this. Also, what type of licensing or copyright info do we need to add, if any? Since we’re already doing this open-source, could we use some type of copyleft or alternate paradigm copyright license? If anyone has thoughts I’m eager to hear them on this one.

We need to change the UI so that the “About App” section can be viewed much more easily from the main screen. Right now you have to hit the three dots in the top right to see it, and hardly any normal users browse there because typically that section only contains licensing info or settings access etc. This is a major problem because the “About App” section has the introduction to what the app is trying to accomplish and what a receptive field even is. By making this more accessible we can probably increase our user engagement and capture rate significantly. I’m thinking it would be best to have a big button in between the homepage description and the image/audio buttons titled “More Information” or something. Again, open to suggestions.

Similar to viewing the generated receptive fields for images, I am having trouble being able to easily and clearly see the generated receptive fields. I know we don’t have a working FastICA implementation yet, but I think this can be done ahead of time. Again, this is really the point of the whole app so this problem is important.

Make sure that the brain picture is centered around text? This may not be an issue really, but for my emulator (running as a Pixel 5) the text is running right up against the brain picture some.

The first screen does not have a picture - a good one needs to be added. This will likely be the first thing people will see when they open the app so choose a good one.

working in albert lab and need access

We should either change some of the slide’s descriptions or add more slides. I think that we can keep the information intelligible to the layman while also giving more accurate information.

When checking the list of recordings that the user has made, there is no back button (this is necessary if the user doesn’t like what they’ve just recorded and wants to try again). Currently the only way to go back is to process one of the current recordings into receptive fields or restart the app. Add a back button.

Yo im continuing from Dr. Albert's NEC lab and I can't push this code without access.

We need to include an option for users to select sample natural stimulus data in addition to their own inputs, to both simplify the task of testing the gabor and gammatone filters and for the user to have immediate access to images and audio input data that they might not be able to currently test(nature pictures or sounds if they're indoors, etc.)

When showing the generated receptive fields for images, in the UI, allow users to click on the receptive fields picture and zoom in to look. Right now in the top left corner and small and hard to see. If the users aren’t able to examine the receptive fields closely and see how cool this all is, the app isn’t doing its job.

For me, usually during the second time I try to process audio into receptive fields it crashes the app. Whoever tackles this will need to attempt to isolate and fix this. This may be happening because our FastICA is absent. Whoever starts working on this, just try it first and we can work on it together if you have any problems. Bugs can be pretty frustrating.

Last but not least. This’ll be the toughest one in my opinion. We’ll need to either find or create a good FastICA implementation in Java. We have several previous attempts that we can build off of and of course successful implementations in other languages to use as well. Dr. Albert has asked that the rest of the app be made launch ready before this so that if we don’t finish it, a new team can just do FastICA and get it over with without having all the time necessary to learn and grok Android Studio as a whole, which I think is a fair point (remember, it’s November and we’re just now getting all our stuff set up since we’re all new to android app dev). We’ll come to this last then.