In “Duh” News, you really shouldn’t try to load everything from an API; there’s just too much.
Going to try loading chunks at a time by checking for a further scroll motion past current limits. I’ve seen it before and it makes sense.
The expandable list items are going to be tricky too, lots of custom array adapters to make.
Got a drawer that updates automatically with available data categories. I think at first I’ll just display all available results from each category in an expandable list.
A filter is still enticing, as is more of a backbone for storing data. So far the idea is to pull each time since there isn’t a real need to store all the data, that’s what the API is for.
I did learn the ADT come with JSON parsing included. It’s an old version but most of the functionality is there and I didn’t need to (nor should I) roll my own; one of the major tenants of software dev is to use tools that are already around; no need to reinvent the wheel every time you build a car.
The Star Wars API is out and it looks like a lot of fun. In my head this is what I want:
- Opening activity with each type of query that loads in the drawer on each app open
- Choose the type of search and a fragment opens to that type of search
- Since we know the schema of each data type (planet, person, ship, etc) we can filter if desired, otherwise everything is returned
- Can also search everything
Results are returned as JSON objects that can be expanded? Don’t know how I want to display that yet.
Mostly I want to play with a Star Wars API and new (to me) Android designs.