Enhance Android App – Fix Bugs + Add Features Via Ai

## Android Kotlin Developer Needed – Improve Existing Finance App + Add New Features

I have an existing Android application that is already developed and published. The app was largely built using AI-assisted development tools such as **Jules**, so I am completely comfortable with the developer using **Jules, Codex, Claude, ChatGPT or other AI coding tools** to speed up development, as long as the final code is clean, working, secure and maintainable.

The project already exists on GitHub.

**GitHub Repository:**
https://github.com/Rivavainfo/Rivavatrackfi-app

**Existing Android App:**
https://play.google.com/store/apps/details?id=com.rivavafi.universal

The application is built primarily using **Kotlin + Jetpack Compose** and already uses technologies including Firebase, Room, Hilt and Retrofit.

### Work Required

I need the existing application reviewed, fixed and improved rather than rebuilt from scratch.

#### 1. Login / Signup Email System

When a new user successfully signs up, automatically send a professional **Welcome / Thank You email**.

If appropriate, also send a login/account confirmation email based on the existing authentication flow.

The email system should be implemented securely through a backend/Cloud Function/API rather than exposing email service credentials inside the Android application.

#### 2. Forgot / Reset Password

Fix and properly implement the **Forgot Password / Reset Password** functionality.

The user should:

Enter their registered email → receive a password-reset email → securely reset their password → return to the app and login normally.

Firebase Authentication is already used in the project.

#### 3. Improve Analytics Section

The app already contains an Analytics section, but I want it improved significantly.

Improve:

- Monthly financial overview
- Income / credit analytics
- Expense / debit analytics
- Profit/savings information
- Better charts and visualizations
- Category breakdowns
- Monthly comparisons
- Clearer empty states
- Better UI/UX
- General calculation/data accuracy

The section should look professional and remain consistent with the existing app design.

#### 4. Add a New "Tools" Section

Create a dedicated financial tools/calculator section with a clean UI.

It should contain:

**Percentage Calculator**

Example:

40% of ₹100 = ₹40

---

**Equivalence / Ratio Calculator**

Example:

100 = 450
200 = ?

Result should automatically calculate the equivalent value.

---

**Profit & Loss Calculator**

Examples:

40% profit on ₹10,000 = ?

20% loss on ₹10,000 = ?

Show original amount, percentage, profit/loss amount and final amount.

---

**Compound Interest Calculator**

Example:

₹1,000 invested for 10 years at 20% annual interest = ?

Show:

- Initial amount
- Interest rate
- Duration
- Final amount
- Total growth/interest earned

---

**MDR Calculator**

Calculation requirement:

For amounts above ₹2,000:

**0.4% of transaction amount**

The MDR charge should be capped at a maximum of **₹300**.

The developer should properly handle amounts below/above the applicable threshold and clearly display the calculation.

---

**EMI Calculator**

Inputs should include:

- Loan amount
- Interest rate
- Loan tenure

Results should include:

- Monthly EMI
- Total interest
- Total payable amount

A simple visual breakdown/chart would be preferred.

### 5. Calculator History

All calculators should have a **calculation history** feature.

Users should be able to:

- See previous calculations
- See calculation type
- See inputs
- See result
- See date/time
- Reopen/reuse a previous calculation
- Delete individual history items
- Clear history

The existing **Room/local database architecture** can be used where appropriate.

### 6. Improve Premium / Secret Key System

The current premium/access system needs to be redesigned.

I do **not** want keys generated using an easily predictable pattern.

Keys should be:

- Randomly generated
- Unique
- Difficult to guess
- Securely stored
- Associated with the correct user/account where required
- Validated securely
- Revocable if required
- Protected from simple APK reverse engineering

Ideally, key generation and verification should happen through **Firebase/Cloud Functions/backend**, rather than storing the real validation logic or master key directly inside the Android application.

### 7. Payment Gateway Integration

If technically and legally feasible, I would also like a payment gateway integrated into the application.

The developer should be able to recommend an appropriate gateway and implement:

Payment → secure server-side verification → update user's payment/premium status → unlock the relevant application features.

Payment status must **never be trusted only from the Android client**.

Webhook/server verification should be implemented wherever required.

### 8. Security Cleanup

Please review the current project for security problems.

This includes:

- Removing hardcoded API secrets
- Moving sensitive credentials out of the APK
- Rotating any credentials that may previously have been exposed
- Protecting backend/API calls
- Securing premium entitlement checks
- Checking Firebase usage
- Checking authentication flows
- Avoiding sensitive information in logs
- General Android security cleanup

### 9. General Bug Fixing

Review the existing application and fix general issues you find, including:

- Crashes
- Navigation problems
- Authentication issues
- UI bugs
- State-management problems
- Data persistence problems
- Incorrect calculations
- Loading-state problems
- Layout problems
- Keyboard/input issues
- Back-button behaviour
- Empty/error states

The goal is to make the application feel much more stable and production-ready.

### 10. UI / Styling Improvements

Please improve inconsistent styling throughout the app while keeping the existing overall Rivava visual identity.

Focus on:

- Consistent spacing
- Typography
- Buttons
- Cards
- Input fields
- Dialogs
- Navigation
- Loading indicators
- Animations where appropriate
- Dark-theme consistency
- Responsive layouts for different Android screen sizes

I am not requesting a completely new design. I want the existing app polished and improved.

## Development Workflow

You can directly work with the existing GitHub repository.

Preferred workflow:

1. Review the existing source code.
2. Create a separate development branch.
3. Implement the requested changes.
4. Test the complete application.
5. Submit the changes through GitHub/PR or push the completed version after approval.

AI-assisted coding tools are allowed and encouraged if they help you complete the project efficiently.

However, copied/generated code must still be reviewed, tested and properly integrated.

## Final Deliverables

At project completion I expect:

- Complete updated source code
- Changes pushed to the GitHub repository or submitted through a pull request
- Working APK for testing
- Release-ready APK/AAB where applicable
- All requested calculators
- Calculator history
- Improved analytics
- Working welcome email
- Working password-reset email
- Improved secure access-key system
- Payment integration if agreed as part of the project
- General bug fixes
- UI/styling improvements
- Security cleanup
- No hardcoded production secrets
- Basic documentation explaining any backend/API configuration required

The updated project should build successfully from a clean checkout.

## Preferred Developer

You should be comfortable with:

**Kotlin, Android, Jetpack Compose, Firebase Authentication, Firestore, Firebase Cloud Functions, Room Database, Hilt, REST APIs, Git/GitHub and payment gateway integrations.**

Experience improving AI-generated or partially AI-generated Android code is a plus.

### When Applying

Please include:

1. Examples of Android/Kotlin apps you have worked on.
2. Your experience with Jetpack Compose.
3. Your Firebase experience.
4. Whether you have implemented payment gateways before.
5. Whether you can work directly with GitHub.
6. Whether you can provide both source code and a test APK.
7. Your estimated fixed project price.

**Please review the repository before bidding instead of sending a generic proposal.**

This can lead to additional long-term development work if the implementation is good.