DiggieDog: A Gopher Client

Semua Versi DiggieDog: A Gopher Client

• 
  1.5.2(16)APK

  Sep 23, 20223.2 MBAndroid 4.1+Yang baru
  Unduh
  Apa yang baru pada versi 1.5.2

  Diperbarui pada Sep 23, 2022

  Updated app to target a more recent version of Android.
  
  Removed Crashlytics, since the old Fabric Crashlytics is gone and I don't want to bring in Firebase.

• 
  1.5.1(15)APK

  Aug 13, 20192.8 MBAndroid 4.1+Yang baru
  Unduh
  Apa yang baru pada versi 1.5.1

  Diperbarui pada Aug 13, 2019

  Fix a crash when presenting phone book directory items.

• 
  1.5(14)APK

  Jul 7, 20182.8 MBAndroid 4.1+Yang baru
  Unduh
  Apa yang baru pada versi 1.5

  Diperbarui pada Jul 7, 2018

  Just fixing a little bug I'd missed where the 'set home page' button would show up for the settings screen etc.. Whoops!

• 
  1.4.1(11)APK

  Jun 1, 20182.8 MBAndroid 4.1+Yang baru
  Unduh
  Apa yang baru pada versi 1.4.1

  Diperbarui pada Jun 1, 2018

  Add opt-in dialogue for crash reports

• 
  1.4(10)APK

  Apr 4, 20182.7 MBAndroid 4.1+Yang baru
  Unduh
  Apa yang baru pada versi 1.4

  Diperbarui pada Apr 4, 2018

  Bookmarking.
  Add in an option to enable/disable javascript in WebViews.

• 
  1.3(9)APK

  Jan 13, 20182.9 MBAndroid 4.1+Yang baru
  Unduh
  Apa yang baru pada versi 1.3

  Diperbarui pada Jan 13, 2018

  Fixed a couple of little bugs. Updated some libraries.

• 
  1.2(7)APK

  Sep 22, 20172.6 MBAndroid 4.1+Yang baru
  Unduh
  Apa yang baru pada versi 1.2

  Diperbarui pada Sep 22, 2017

  Fixes an issue with the auto-type detect for unrecognised gopher types.

• 
  1.1(5)APK

  Aug 29, 20172.6 MBAndroid 4.1+Yang baru
  Unduh
  Apa yang baru pada versi 1.1

  Diperbarui pada Aug 29, 2017

  Removed ads. Fixed an issue with deep linking. Fixed issues with save button potentially obscuring content.

• 
  1.0.2(4)APK

  Jul 30, 20173.6 MBAndroid 4.1+Yang baru
  Unduh
  Apa yang baru pada versi 1.0.2

  Diperbarui pada Jul 30, 2017

  Fixed a crash when putting in a super big port number!
  Also fixed a little issue with the history items having nulls in the path; not a crash, but kinda ugly to look at. Unfortunately my rigorous QA process had let that one through :(