An application does not require a significant amount of processing or frame-rate speed can be written on a view
-
True
-
False
The statement is True. For applications that don't require intensive processing or high frame rates (like static forms or simple UIs), using a View is appropriate and more efficient. Views handle invalidation and redraws automatically when content changes, making them suitable for low-frequency updates.
This is the counterpart fact to the Canvas/SurfaceView question: an app that doesn't need high frame-rate or heavy continuous processing (e.g., a simple UI with occasional updates) can simply extend/override a standard View and do its custom drawing in onDraw(), relying on the normal View lifecycle. It's only when performance demands (smooth animation, real-time rendering) exceed what the standard View pipeline can efficiently deliver that developers move to drawing directly on a Canvas via a dedicated SurfaceView on a separate thread. So writing lightweight graphics 'on a view' being True correctly reflects Android's tiered approach to custom drawing based on performance needs.