rfc1459 / moca Goto Github PK

To get the application promoted from draft stage, we need the following promotional material:

• high res icon for badge DONE
• screenshots (at least two) DONE
• application description (italian) DONE
• application description (english) DONE
• privacy policy statement (a wiki page on GitHub is fine)

The following items are optional, but nevertheless they should be provided to ensure proper visibility on the store:

• feature graphic (used in the "Featured" section of Play Store) DONE
• promotional graphic (used almost everywhere in Play Store)

Hardly anything to say except that the map cannot be hosted reliably inside a fragment due to MapActivity and FragmentActivity stomping on each other's lifecycle.

The application should not die if the twitter client encounters an I/O error. FIX IT. NOW.

The application should launch Giggity if installed or redirect the user to the appropriate entry in the Play Store.

Static data (Home screen, FAQs, banners) should be synchronized off the network instead of being bundled with the app. This would make it possible to release updates only for bugfixes and functional changes in the application code.

Forcing people to redownload the whole APK for a minor aesthetic change sucks.

This is fairly straightforward to implement, both fragments should contain just a ListView of bitmaps and URLs.

While rewriting all UI code, tablet layout and support code got lost in space. Rewrite them.

Since I'm a complete noob with Pescarese dialect, the following resources should be translated into Pescarese by someone more knowledgeable than myself:

• res/raw-it-rPE/home.json (missing, use res/raw-it/home.json as a template)
• res/raw-it-rPE/faq.json (missing, use res/raw-it/faq.json as a template)
• res/values-it-rPE/strings.xml (use res/values/strings.xml as a template for missing entries, ignore those marked with MissingTranslation)

The first two files are mostly static, while the last one is modified often.