Introduction

Yes, you can reproduce android:layout_below at runtime, but you do it through RelativeLayout.LayoutParams rather than by editing XML attributes directly. The key idea is to update the target view’s layout rules in code and make sure both the anchor view and the moving view have valid IDs.

layout_below in XML Maps to addRule in Code

In XML, a RelativeLayout rule might look like this:

android:layout_below="@id/titleView"

At runtime, the equivalent is:

params.addRule(RelativeLayout.BELOW, titleView.getId());

That means the programmatic solution has three moving parts:

• the parent must be a RelativeLayout
• the anchor view must have an ID
• the target view must use RelativeLayout.LayoutParams

If any of those are missing, the rule will not behave the way you expect.

A Complete Runtime Example

Here is a small Java example that places one TextView below another in code:

1RelativeLayout parent = new RelativeLayout(this);
2
3TextView titleView = new TextView(this);
4titleView.setId(View.generateViewId());
5titleView.setText("Title");
6
7RelativeLayout.LayoutParams titleParams =
8        new RelativeLayout.LayoutParams(
9                RelativeLayout.LayoutParams.WRAP_CONTENT,
10                RelativeLayout.LayoutParams.WRAP_CONTENT
11        );
12titleParams.addRule(RelativeLayout.ALIGN_PARENT_TOP);
13parent.addView(titleView, titleParams);
14
15TextView subtitleView = new TextView(this);
16subtitleView.setId(View.generateViewId());
17subtitleView.setText("Subtitle");
18
19RelativeLayout.LayoutParams subtitleParams =
20        new RelativeLayout.LayoutParams(
21                RelativeLayout.LayoutParams.WRAP_CONTENT,
22                RelativeLayout.LayoutParams.WRAP_CONTENT
23        );
24subtitleParams.addRule(RelativeLayout.BELOW, titleView.getId());
25parent.addView(subtitleView, subtitleParams);

This is the direct runtime equivalent of defining the relationship in XML.

If the view already exists in your layout, you usually retrieve and modify its existing layout params instead of creating new views from scratch.

Updating an Existing View at Runtime

If both views are already in the layout, the pattern is shorter:

1TextView titleView = findViewById(R.id.titleView);
2TextView subtitleView = findViewById(R.id.subtitleView);
3
4RelativeLayout.LayoutParams params =
5        (RelativeLayout.LayoutParams) subtitleView.getLayoutParams();
6
7params.addRule(RelativeLayout.BELOW, titleView.getId());
8subtitleView.setLayoutParams(params);

If you need to move the view again later, clear or replace conflicting rules before applying the new one. Otherwise, the view may keep old positioning constraints that fight with the new rule.

For example, on newer Android APIs:

params.removeRule(RelativeLayout.ABOVE);
params.addRule(RelativeLayout.BELOW, titleView.getId());
subtitleView.setLayoutParams(params);

That makes the layout change explicit and avoids stale constraints.

IDs Matter More Than People Expect

The most common reason this fails is missing IDs. XML views usually have them already, but dynamically created views do not unless you assign one.

view.setId(View.generateViewId());

Without a valid ID on the anchor view, RelativeLayout.BELOW has nothing reliable to reference.

Also note that layout_below is specifically a RelativeLayout concept. If your parent is LinearLayout, FrameLayout, or ConstraintLayout, the same code will not apply. In modern Android, ConstraintLayout is often preferred for new screens, and it has its own separate programmatic constraint APIs.

Common Pitfalls

The biggest mistake is trying to use RelativeLayout rules on a view whose parent is not a RelativeLayout. The layout params must match the parent layout type.

Another issue is forgetting to assign an ID to a dynamically created anchor view. Without that ID, the BELOW rule cannot target anything meaningful.

Developers also sometimes modify layout params and forget to set them back on the view. If the updated params are never reapplied, nothing changes on screen.

Finally, if the UI design is heavily dynamic, consider whether ConstraintLayout or a different layout structure would be easier to maintain than piling more RelativeLayout rules into runtime code.

It is also worth testing the result on different screen sizes after the rule change. A programmatic layout update that looks correct on one device can still expose hidden spacing or overlap assumptions elsewhere in the view hierarchy.

Summary

• Yes, android:layout_below can be set programmatically.
• The runtime equivalent is RelativeLayout.LayoutParams.addRule(RelativeLayout.BELOW, anchorId).
• Both the anchor and the moving view need valid IDs.
• The parent layout must actually be a RelativeLayout.
• If views are repositioned repeatedly, clear conflicting rules before applying new ones.