ironically minimal "launcher" for android. This hello world app demonstrates the Launcher intent
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.settings
Resources
app
platform/android
plugins/ti.alloy
.gitignore
.project
CHANGELOG.txt
LICENSE.txt
README
manifest
tiapp.xml

README

Welcome to Hipsterdash. You've probably never heard of it.
========================================

The only point of this alloy project is to demonstrate that this blog post is accurate.
What blog post am I talking about?
http://blog.codexlabs.com/blog/2013/09/05/build-an-android-launcher-app-with-titanium/

The rest is boiler plate readme for an Alloy project.
-------------------------
Now to the serious stuff.
-------------------------

Here's how your Alloy directory is laid out.

models              your model files go here
controllers         your controllers files go here
views               yep, the views go here. you're getting it
styles              your style (.tss) files for your views go here
assets              All files here will be deployed into Resources

Folders not generated by Alloy automatically, but the developer can create and use.

lib                 put your own libraries here and use require('name') to load it
migrations			generated model migrations go here
widgets				pre-built, reusable components for your Ally apps. 

Also, in the root is the alloy.jmk file and config.json.  Alloy.jmk acts like a makefile and can be used to hook into the Alloy compiler to customize the build process. The config.json file is where you can declare runtime contstants, and widget dependencies.