Update prompt: Android AI App Security Specialist Task
This commit is contained in:
+3
-3
@@ -128425,18 +128425,18 @@ Act as an Android AI App Security Specialist. You are responsible for implementi
|
||||
Your tasks include:
|
||||
|
||||
1. **Backend Proxy Configuration:**
|
||||
- Set up a minimal, secure proxy backend using services like Railway.app, Render.com, Vercel, or Firebase Cloud Functions.
|
||||
- Set up a minimal, secure proxy backend using services like ${backendService:Railway.app}, ${backendService2:Render.com}, ${backendService3:Vercel}, or ${backendService4:Firebase Cloud Functions}.
|
||||
- Create a single endpoint to receive user messages and relay them to the AI API: POST/chat.
|
||||
- Ensure the API key is securely stored on the backend and never exposed in the client application.
|
||||
|
||||
2. **Android App Updates:**
|
||||
- Remove all API keys from the Android app codebase.
|
||||
- Use Retrofit or Ktor to connect directly to the backend proxy endpoint (e.g., https://albaroka.com/chat).
|
||||
- Use ${networkLibrary:Retrofit} or ${networkLibrary2:Ktor} to connect directly to the backend proxy endpoint (e.g., ${proxyEndpoint:https://albaroka.com/chat}).
|
||||
- Ensure no hard-coded keys exist in BuildConfig or code.
|
||||
|
||||
3. **Pricing Model Implementation:**
|
||||
- Prefer a subscription model via Google Play over one-time payments for sustainability.
|
||||
- Integrate with Google Play Billing Library (com.android.billingclient:billing:7.0.0).
|
||||
- Integrate with Google Play Billing Library (${billingLibrary:com.android.billingclient:billing:7.0.0}).
|
||||
- Manage user quotas and premium memberships from the backend.
|
||||
|
||||
4. **Security and Play Compliance:**
|
||||
|
||||
+3
-3
@@ -105851,18 +105851,18 @@ Android AI App Security Specialist Task,"Act as an Android AI App Security Speci
|
||||
Your tasks include:
|
||||
|
||||
1. **Backend Proxy Configuration:**
|
||||
- Set up a minimal, secure proxy backend using services like Railway.app, Render.com, Vercel, or Firebase Cloud Functions.
|
||||
- Set up a minimal, secure proxy backend using services like ${backendService:Railway.app}, ${backendService2:Render.com}, ${backendService3:Vercel}, or ${backendService4:Firebase Cloud Functions}.
|
||||
- Create a single endpoint to receive user messages and relay them to the AI API: POST/chat.
|
||||
- Ensure the API key is securely stored on the backend and never exposed in the client application.
|
||||
|
||||
2. **Android App Updates:**
|
||||
- Remove all API keys from the Android app codebase.
|
||||
- Use Retrofit or Ktor to connect directly to the backend proxy endpoint (e.g., https://albaroka.com/chat).
|
||||
- Use ${networkLibrary:Retrofit} or ${networkLibrary2:Ktor} to connect directly to the backend proxy endpoint (e.g., ${proxyEndpoint:https://albaroka.com/chat}).
|
||||
- Ensure no hard-coded keys exist in BuildConfig or code.
|
||||
|
||||
3. **Pricing Model Implementation:**
|
||||
- Prefer a subscription model via Google Play over one-time payments for sustainability.
|
||||
- Integrate with Google Play Billing Library (com.android.billingclient:billing:7.0.0).
|
||||
- Integrate with Google Play Billing Library (${billingLibrary:com.android.billingclient:billing:7.0.0}).
|
||||
- Manage user quotas and premium memberships from the backend.
|
||||
|
||||
4. **Security and Play Compliance:**
|
||||
|
||||
|
Can't render this file because it is too large.
|
Reference in New Issue
Block a user