How deean55/cti-cart-app works
CTI-CART appears to be an Android app for machinery listings and buyer/seller RFQs, with authentication, listing, discovery, and communication screens. The graph organizes the visible source files into those product areas and includes the Firebase repository and domain models. No application source excerpts or README were provided, so runtime relationships are shown only as dashed, unverified links inferred from filenames; the actual routing and data calls could not be confirmed.
Main entry points: MainActivity.kt Main activity · FirebaseRepository.kt Firebase repository · AddMachineScreen.kt Add machine · PostRFQScreen.kt Post RFQ
Components 26
App entry
- Main activity
app/src/main/java/com/example/cti_cart/MainActivity.kt
Identity and onboarding
- Login
app/src/main/java/com/example/cti_cart/ui/screens/LoginScreen.kt - OTP login
app/src/main/java/com/example/cti_cart/ui/screens/OtpLoginScreen.kt - Registration
app/src/main/java/com/example/cti_cart/ui/screens/RegisterScreen.kt - Role selection
app/src/main/java/com/example/cti_cart/ui/screens/RoleSelectionScreen.kt - Welcome
app/src/main/java/com/example/cti_cart/ui/screens/WelcomeScreen.kt - Splash
app/src/main/java/com/example/cti_cart/ui/screens/SplashScreen.kt - User model
app/src/main/java/com/example/cti_cart/model/User.kt
Machine marketplace
- Dashboard
app/src/main/java/com/example/cti_cart/ui/screens/DashboardScreen.kt - Machine listings
app/src/main/java/com/example/cti_cart/ui/screens/MachineListScreen.kt - Machine card
app/src/main/java/com/example/cti_cart/ui/components/MachineCard.kt - Add machine
app/src/main/java/com/example/cti_cart/ui/screens/AddMachineScreen.kt - Machine forms
app/src/main/java/com/example/cti_cart/ui/machineforms/MachineForms.kt - Map picker
app/src/main/java/com/example/cti_cart/ui/screens/MapPickerScreen.kt - Machine model
app/src/main/java/com/example/cti_cart/model/Machine.kt
RFQ and communication
- Post RFQ
app/src/main/java/com/example/cti_cart/ui/screens/PostRFQScreen.kt - My RFQs
app/src/main/java/com/example/cti_cart/ui/screens/MyRFQsScreen.kt - Buyer RFQs
app/src/main/java/com/example/cti_cart/ui/screens/BuyerRFQsScreen.kt - RFQ components
app/src/main/java/com/example/cti_cart/ui/screens/RFQComponents.kt - RFQ model
app/src/main/java/com/example/cti_cart/model/RFQ.kt - Chat
app/src/main/java/com/example/cti_cart/ui/screens/ChatScreen.kt - Drawing viewer
app/src/main/java/com/example/cti_cart/ui/screens/DrawingViewerScreen.kt - Add details
app/src/main/java/com/example/cti_cart/ui/screens/AddDetailsScreen.kt - Firebase repository
app/src/main/java/com/example/cti_cart/data/FirebaseRepository.kt
Other components
- App user
- Firebase services
Connections 27
- App user → Main activity: opens app
- Main activity → Splash: may route
- Main activity → Welcome: may route
- Main activity → Login: may route
- Main activity → OTP login: may route
- Main activity → Registration: may route
- Main activity → Role selection: may route
- Main activity → Dashboard: may route
- Main activity → Machine listings: may route
- Main activity → Add machine: may route
- Main activity → Post RFQ: may route
- Main activity → My RFQs: may route
- Main activity → Buyer RFQs: may route
- Main activity → Chat: may route
- Main activity → Map picker: may route
- Machine listings → Machine card: may render
- Add machine → Machine forms: may use
- Add machine → Map picker: may use
- Post RFQ → RFQ components: may use
- My RFQs → RFQ model: may display
- Buyer RFQs → RFQ model: may display
- Post RFQ → RFQ model: may create
- Chat → Firebase repository: may call
- Machine listings → Firebase repository: may call
- Add machine → Firebase repository: may call
- Post RFQ → Firebase repository: may call
- Firebase repository → Firebase services: may access