Suggesting items/spells/feats

[tsiemens]

Should have set of items, spells, armors, weapons, feats, which can be searched.
Should autocomplete most attributes of the item.

UI undecided.

[tsiemens]

Possible direction for this would be to have all data in string resources as an array (preferably not actually in strings.xml though, maybe split into feats.xml, etc.), and parse the data. Eg.
"Item Name|stat1|stat2|stat3|description_resource_id"

possibly very long description

[samcorcoran]

The unofficial pathfinder wiki, d20pfsrd, has spreadsheets with a lot of content:
http://www.d20pfsrd.com/feats/feats-db
http://www.d20pfsrd.com/traits/tools/traits-db
http://www.d20pfsrd.com/magic/tools/spells-db
http://www.d20pfsrd.com/bestiary/tools/monster-filter
http://www.d20pfsrd.com/magic-items/magic-items-db
http://www.d20pfsrd.com/extras/consolidated-lists/equipment
which can be exported as CSV files. You could potentially use it in that format, or write a script to process it all into an XML format you could use instead.

It may be of interest to note that "Pathfinder Open Reference", another Pathfinder android app (which essentially acts as a mobile copy of all pathfinder reference material) stores its content in a database. It's code is open source and can be found here:
https://github.com/devonjones/PathfinderOpenReference

[tsiemens]

If this approach is taken, most likely what would be more desirable is to be able to download these on the fly to the app, and construct a few new tables in which to cache them. This way, if there are any updates to them, we don't need to push an app update, and it reduces the download size of the core app.

[samcorcoran]

That would also help with not taking issue #2 (translations) backwards. If the app is populated with large volumes of English content then translation would be very long-winded, and involve a lot of duplication.

If tables can be switched in and out then users could opt to use, for example, French equipment and spell tables, even if feat and monster tables have not yet been translated.

Did you intend "on-the-fly" table use to involve users using the app to query a central server for up-to-date content (like a newspaper app might do to download the latest news articles), or did you mean that users could manually copy up-to-date tables into their device's file system?

[tsiemens]

By this I meant there would be a refresh button for each table located wherever convenient, which would automatically download from the export URL linked on the d20 pages. This is assuming that those will remain relatively constant.

The other option would be to have downloadable files from the repository (via raw.github.com), so that I am not solely responsible for updating the tables when they are updated.