Rapid Tasker Prototyping
We’re going to start prototyping the widget using Tasker instead of going straight for the gold and coding a native version using AIDE. That’s because our end product will morph based on how we end up using the widget. Using this approach, we can quickly implement design modifications and see immediately how these changes affect the experience. This is especially important early in the development phase, where we still might not know exactly what features we want to emphasize.
If we were to modify the native Java version, we would have to go through a compile, deploy, and testing phase compared to Tasker’s two-step edit-and-run process. We would also need to lug around a keyboard if we were to make a large modification ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access