StargazeSign in
MAMas

Probe

Probe — see your iOS app from every angle. Mobile companion in SwiftUI.

Closed sourcesaasSwift0
Share on X

★ Embed badge

Paste it in your README. Updates live as you collect right-swipes.

Markdown[![Stargaze](https://stargaze.ashlr.ai/api/badge/probe-925ee3.svg)](https://stargaze.ashlr.ai/p/probe-925ee3)
HTML<a href="https://stargaze.ashlr.ai/p/probe-925ee3"><img src="https://stargaze.ashlr.ai/api/badge/probe-925ee3.svg" alt="Stargaze" /></a>
URLhttps://stargaze.ashlr.ai/api/badge/probe-925ee3.svg

From the README

Probe

Generated by Morphkit from web source analysis.

Project Stats

  • Total files: 179
  • High confidence: 132
  • Medium confidence: 47
  • Low confidence: 0

Structure

Probe/
├── ProbeApp.swift       # App entry point
├── ContentView.swift          # Root navigation
├── Models/                    # Codable data models
├── Views/                     # SwiftUI views
├── Navigation/                # Router and routes
├── Networking/                # API client and DTOs
├── State/                     # Observable stores
└── Assets.xcassets/           # Colors and images

Requirements

  • Xcode 15+
  • iOS 17+
  • Swift 5.9+

Warnings

  • [Views/HomeView.swift] Screen "Home" uses custom layout — generated best-effort view from components and data requirements
  • [Views/DashboardView.swift] Dashboard layout generated — review hero section copy and featured item selection
  • [Views/AnalyticsView.swift] No components or data requirements defined for screen "Analytics" — generated layout from metadata
  • [Views/TeamBillingView.swift] Screen "TeamBilling" uses custom layout — generated best-effort view from components and data requirements
  • [Views/TeamInviteView.swift] Screen "TeamInvite" uses custom layout — generated best-effort view from components and data requirements
  • [Views/TeamAllocationsView.swift] Screen "TeamAllocations" uses custom layout — generated best-effort view from components and data requirements
  • [Views/SectionCardView.swift] No components or data requirements defined for screen "SectionCard" — generated layout from metadata
  • [Views/SectionCardView.swift] Screen "SectionCard" uses custom layout — generated best-effort view from components and data requirements
  • [Views/CodeBlockView.swift] No components or data requirements defined for screen "CodeBlock" — generated layout from metadata
  • [Views/CodeBlockView.swift] Screen "CodeBlock" uses custom layout — generated best-effort view from components and data requirements
  • [Views/BadgeView.swift] No components or data requirements defined for screen "Badge" — generated layout from metadata
  • [Views/BadgeView.swift] Screen "Badge" uses custom layout — generated best-effort view from components and data requirements
  • [Views/DashboardPageView.swift] Dashboard layout generated — review hero section copy and featured item selection
  • [Views/HeatmapRowView.swift] No components or data requirements defined for screen "HeatmapRow" — generated layout from metadata
  • [Views/HeatmapRowView.swift] Screen "HeatmapRow" uses custom layout — generated best-effort view from components and data requirements
  • [Views/ActivityTooltipView.swift] No components or data requirements defined for screen "ActivityTooltip" — generated layout from metadata
  • [Views/ActivityTooltipView.swift] Screen "ActivityTooltip" uses custom layout — generated best-effort view from components and data requirements
  • [Views/StatCardView.swift] Screen "StatCard" uses custom layout — generated best-effort view from components and data requirements
  • [Views/DepthMiniCardView.swift] No components or data requirements defined for screen "DepthMiniCard" — generated layout from metadata
  • [Views/DepthMiniCardView.swift] Screen "DepthMiniCard" uses custom layout — generated best-effort view from components and data requirements
  • [Views/DepthBadgeView.swift] Screen "DepthBadge" uses custom layout — generated best-effort view from components and data requirements
  • [Views/DiffViewView.swift] No components or data requirements defined for screen "DiffView" — generated layout from metadata
  • [Views/DiffViewView.swift] Screen "DiffView" uses custom layout — generated best-effort view from components and data requirements
  • [Views/ResearchSummaryView.swift] Screen "ResearchSummary" uses custom layout — generated best-effort view from components and data requirements
  • [Views/TocLinkView.swift] Screen "TocLink" uses custom layout — generated best-effort view from components and data requirements
  • [Views/FollowUpMessageView.swift] Screen "FollowUpMessage" uses custom layout — generated best-effort view from components and data requirements
  • [Networking/SupabaseManager.swift] Update SUPABASE_URL and SUPABASE_ANON_KEY in SupabaseManager
  • [Networking/PaymentManager.swift] Update checkout URL in PaymentManager to match your Stripe integration
  • [State/ScheduleStore.swift] ScheduleStore uses inferred API methods — verify method names match APIClient
  • [State/AnnotationStore.swift] AnnotationStore uses inferred API methods — verify method names match APIClient
  • [State/MemoryStore.swift] MemoryStore uses inferred API methods — verify method names match APIClient
  • [State/IntegrationStore.swift] IntegrationStore uses inferred API methods — verify method names match APIClient
  • [State/TransactionStore.swift] TransactionStore uses inferred API methods — verify method names match APIClient
  • [State/InviteStore.swift] InviteStore uses inferred API methods — verify method names match APIClient
  • [State/AllocationStore.swift] AllocationStore uses inferred API methods — verify method names match APIClient
  • [State/DashboardViewModel.swift] DashboardViewModel state types are inferred — verify and replace with concrete types
  • [State/SettingsViewModel.swift] SettingsViewModel state types are inferred — verify and replace with concrete types
  • [State/HistoryViewModel.swift] HistoryViewModel state types are inferred — verify and replace with concrete types
  • [State/TeamViewModel.swift] TeamViewModel state types are inferred — verify and replace with concrete types
  • [State/CollectionsViewModel.swift] CollectionsViewModel state types are inferred — verify and replace with concrete types
  • [State/TemplatesViewModel.swift] TemplatesViewModel state types are inferred — verify and replace with concrete types
  • [State/ConnectEveroViewModel.swift] ConnectEveroViewModel state types are inferred — verify and replace with concrete types
  • [State/VerifyEmailViewModel.swift] VerifyEmailViewModel state types are inferred — verify and replace with concrete types
  • [State/UpdatePasswordViewModel.swift] UpdatePasswordViewModel state types are inferred — verify and replace with concrete types
  • [State/MfaVerifyViewModel.swift] MfaVerifyViewModel state types are inferred — verify and replace with concrete types
  • [State/RegisterViewModel.swift] RegisterViewModel state types are inferred — verify and replace with concrete types
  • [State/ResetPasswordViewModel.swift] ResetPasswordViewModel state types are inferred — verify and replace with concrete types
  • [State/ResearchDetailViewModel.swift] ResearchDetailViewModel state types are inferred — verify and replace with concrete types
  • [State/TeamSettingsViewModel.swift] TeamSettingsViewModel state types are inferred — verify and replace with concrete types
  • [State/AnalyticsPageViewModel.swift] AnalyticsPageViewModel state types are inferred — verify and replace with concrete types
  • [State/BillingContentViewModel.swift] BillingContentViewModel state types are inferred — verify and replace with concrete types
  • [State/LoginFormViewModel.swift] LoginFormViewModel state types are inferred — verify and replace with concrete types
  • [State/TeamBillingContentViewModel.swift] TeamBillingContentViewModel state types are inferred — verify and replace with concrete types
  • [State/InviteContentViewModel.swift] InviteContentViewModel state types are inferred — verify and replace with concrete types
  • [State/AllocationsContentViewModel.swift] AllocationsContentViewModel state types are inferred — verify and replace with concrete types
  • [State/CollectionDetailPageViewModel.swift] CollectionDetailPageViewModel state types are inferred — verify and replace with concrete types
  • [Assets.xcassets/AppIcon.appiconset/Contents.json] Add a 1024x1024 app icon image

Getting Started

Open Package.swift in Xcode to build and run the project.

Notes

This project was automatically generated and may need manual adjustments:

  1. Replace placeholder API base URL in Networking/APIConfiguration.swift.
  2. Add app icon to Assets.xcassets/AppIcon.appiconset/.
  3. Review all files marked with "medium" or "low" confidence.

Like what you see?

Star this on Stargaze — auto-stars on GitHub when you swipe right.

Star this on Stargaze