<!--
{
  "availability" : [
    "iOS: 2.0.0 -",
    "iPadOS: 2.0.0 -",
    "macCatalyst: 13.1.0 -",
    "tvOS: -",
    "visionOS: 1.0.0 -"
  ],
  "documentType" : "symbol",
  "framework" : "UIKit",
  "identifier" : "/documentation/UIKit/UIResponder/next",
  "metadataVersion" : "0.1.0",
  "role" : "Instance Property",
  "symbol" : {
    "kind" : "Instance Property",
    "modules" : [
      "UIKit"
    ],
    "preciseIdentifier" : "c:objc(cs)UIResponder(py)nextResponder"
  },
  "title" : "next"
}
-->

# next

Returns the next responder in the responder chain, or `nil` if there’s no next responder.

```
var next: UIResponder? { get }
```

## Return Value

The next object in the responder chain, or `nil` if this is the last object in the chain.

## Discussion

The [`UIResponder`](/documentation/UIKit/UIResponder) class doesn’t store or set the next responder automatically, so this method returns `nil` by default. Subclasses must override this method and return an appropriate next responder. For example, [`UIView`](/documentation/UIKit/UIView) implements this method and returns the [`UIViewController`](/documentation/UIKit/UIViewController) object that manages it (if it has one) or its superview (if it doesn’t). [`UIViewController`](/documentation/UIKit/UIViewController) similarly implements the method and returns its view’s superview. [`UIWindow`](/documentation/UIKit/UIWindow) returns the application object. The shared [`UIApplication`](/documentation/UIKit/UIApplication) object normally returns `nil`, but it returns its app delegate if that object is a subclass of [`UIResponder`](/documentation/UIKit/UIResponder) and hasn’t already been called to handle the event.

---

Copyright &copy; 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)