In VSCode using 'iOS Debug' it's possible to build & debug iOS Simulator applications. https://marketplace.visualstudio.com/items?itemName=nisargjhaveri.ios-debug

I'm wondering whether there might be interest in using VSCode to hot reload:

Bam!

Also:

• Removed extraneous asset catalogs (all targets share the same one now)
• Changed a few conditional statements to exclude tvOS instead of including all 3 other platforms (little cleaner)

Known issues

• Certain views don’t scroll, like FontsGrouping. May need an explicit ScrollView

• Add watchOS app!
• Exclude unsupported components with #if os statements
• Update Readme + add useful Apple links
• Add system images section in the Images group
• Refactor var lineColor to be a color set in the asset library instead (initially to avoid a big, ugly if else block but seems to be the better approach)
• Add renderingMode(.original) modifier example for multi-color system images
• Add frame constraints to the shapes examples so they don’t stretch out too much when resizing windows on macOS

Fix the mismatched case of the image name. I had to change the name of the image, as just changing the case of the 'i' in the asset catalog didn't show up in git.

This might be a bug with SwiftUI itself (not the first time I’m seeing this with Sidebar(), but capturing here in case someone knows a fix.

When entering in full screen mode, the first button in the sidebar view is hidden by the toolbar.

I am not sure if you plan to extend the app for macOS, but if so, I have a first draft.

• Modified ControlsGroup and FontsGroup to use SectionView
• Add target, create folder for target specific files
• Move unsupported things behind os check (Haptic, ActionSheet)
• Fix compilation errors (UIColor -> NSColor)
• Add close button to sheet
• Add scrollview and frames modifier to content is visible
• Style SectionView because a macOS Section is without any styling

Known problems:

• [x] Icon does not look like a Big Sur icon
• [ ] Navigation Link button not working
• [ ] When making window very thin some lables get cutoff, not sure why
• [x] Sheet needs styling

• Add the .destructive button style for the action sheet component
• Add a second default button to further emphasize that the action sheet is meant to be used to present explicit options for the user to choose from (instead of the "OK"/"Done" dismissal which is usually better suited for an alert)
• Add *.DS_Store to gitignore cuz it’s annoying

Per the HIG, the destructive style is the first option presented (reference).

Love this repo – so helpful! Something Apple should provide themselves.

Previews for extracted views (like the files in the Groupings folder) are shown in an iPhone frame by default (since the scheme is set to iPhone SE) – I wonder if it would make sense to change the preview layout to .previewLayout(.sizeThatFits) for these.

Having the iPhone chrome can imply/suggest that it’s a "screen" rather than an isolated piece of UI (I can see this being confusing for someone starting out who isn’t familiar with breaking up views in multiple files).

I can create a PR for it but wanted to check first!

Updated preview would look like this:

It works, so why don't show it :)

However, the Divider() looks a bit weird:

But I think we should still show it as the app helps people to show what the elements are going to look like.

Add sample Top Shelf images for tvOS to show where "Top Shelf" asset are used.

More about Top Shelf assets: https://developer.apple.com/design/human-interface-guidelines/tvos/overview/top-shelf/

Now that multiple targets are sharing the same code, I’ve rearranged the folder structure a little bit to better mirror Apple’s new Multiplatform boilerplate project in Xcode 12 and simplify folder names.

• The Shared folder contains all the shared code (most of it, really)
• Platform-specific folders contain their own info.plist and entitlements

No functional changes otherwise!

Feature:

• now that SwiftUI 2.0 has SceneView supported by SceneKit, we can add a row under Maps for an example of SceneKit.

Implementation

• All we need is a model with extension .usdz and a few lines of code to implement this feature. you can preview implementation in the readMe of this repository

How should we be thinking about modeling the views, especially those that differ by platform and as the repo grows over time?

Could imagine the #if method getting messy.

As I was building this in the first place, I imagined making a struct to hold each grouping and an array of views inside of it. Curious if there are other suggestions and if doing this might be overkill?

The app reminds me a little bit of an app I've used before: Fiori Mentor

It offers the option to copy the code directly from within the app, see here. Maybe we could offer something similar?

Disclosure: The app was developer by my employer, however I was not involved.