[hemmerling] Cleaning Service 3/3 - Implementation

Related pages:

• Cleaning.
• Cleaning Service 1/3 ( Minimum Viable Product ).
• Cleaning Service 2/3.
• Reinigungssservice 1/2 ( Minimum Viable Product ).
• Reinigungssservice 2/2.

• Implementation.
  • Design principle “Minimum Viable Product”.
  • Stock implementation “Clean Funnel”, custom implementation “WirReinigenBeiEuch”.
  • To add new service providers ( = customers of the portal ):
    1. Creating a directory at ”/php/sales/”. Example: Service provider #2 ⇒ ”/php/sales/0002”.
    2. Add suitable “sales.php” and ”.htaccess” files. Example: Service provider #2 ⇒ ”/php/sales/0002/sales.php”, ”/php/sales/0002/.htaccess”.
    3. Add a suitable ”.htpasswd” file. Example: Service provider #2 ⇒ ”/txt/sales0002.xampp/.htpasswd”, ”/txt/sales0002.htpasswd”.
• Code:
  • Access control based on ”.htaccess” and ”.htpasswd” for administration and service providers.
    • Preconfigured access for administration: Username “admin”, password “admin”.
    • Preconfigured access for the sales staff of service providers: Username “sales”, password “sales”.
    • Procedural style.
    • Supported PHP ecosystems: Plain PHP4 ( 2000 - 2008, MySQL ) / PHP5 ( 2004 - 2018, MySQL ) & PHP7 ( 2015 -, MySQLi ), framework-free.
    • Tested with
      • PHP 4.4.3 ( Free.fr ).
      • PHP 5.3.8, PHP 8.2.4 ( XAMPP ).
      • PHP 7.4.33 ( Debian Linux ).
• Supported browsers:
  • Firefox on Windows, Debian Linux, Android.
  • Google Chrome on Windows, Android.
  • Microsoft Edge, Microsoft Internet Explorer 11 ( MSIE11 ) on Windows.

• Project name: “WirReinigenBeiEuch”.
• Java Name: “com.hemmerling.wirreinigenbeieuch”.
• API: “17 ( Android 4.2 ).
• Default path on Windows “C:\Users\Administrator\AndroidStudioProjects”.

• App Status: Rejected
• Your app has been rejected and wasn't published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play
• Issue found: Violation of Broken Functionality policy. Your app contains content that isn’t compliant with the Broken Functionality policy. App contains icon(s) or button(s) that are not responsive or do not return content.
• Issue details. We found an issue in the following area(s): Version code 2: In-app experience
• To bring your app into compliance, follow these steps: Make sure to fix all broken experiences within your app. You can use the pre-launch and crash reports available in the Play Console to check for app stability.

• The app might not collect and process data, but there is just a single button, which loads an URL in browser's default smartphone, i.e. the “homepage” of the application.