diff --git a/README.md b/README.md
index 2a5744a9a7631393e0b28892acb36a4522b7eb1d..54894912799fcf7d0cb8f6cfbacdf3512ec78a1b 100644
--- a/README.md
+++ b/README.md
@@ -1,92 +1,6 @@
-# Nyan-Cat
+nyan cat fun
 
+using function 
+loading image
 
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://git.flow3r.garden/chubbson/nyan-cat.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://git.flow3r.garden/chubbson/nyan-cat/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+image should not be grater than 240 or must be a square? it crashes otherwise
\ No newline at end of file
diff --git a/__init__.py b/__init__.py
new file mode 100644
index 0000000000000000000000000000000000000000..fb7686635a2b91bb85df8af7c2107aedae2d4ecc
--- /dev/null
+++ b/__init__.py
@@ -0,0 +1,55 @@
+from st3m.application import Application, ApplicationContext
+import st3m.run
+import leds
+import uos
+
+class NyanCat(Application):
+    def __init__(self, app_ctx: ApplicationContext) -> None:
+        super().__init__(app_ctx)
+        self.picidx: int = 0; 
+
+    def draw(self, ctx: Context) -> None:
+        # Paint the background black
+        ctx.rgb(0, 0, 0).rectangle(-120, -120, 240, 240).fill()
+
+        path = self.nextImage(ctx)
+        ctx.image(path, -120, -120, 241, 241)
+
+        # colorful petals
+        leds.set_brightness(10)
+        for i in range(40):
+            if i % 8 == 0:
+                # paint all tips 
+                leds.set_rgb(i, 0, 0, 0)   
+            elif i // 8 == 0:
+                # yellow
+                leds.set_rgb(i, 255, 255, 0)
+            elif i // 8 == 1:
+                # pink
+                leds.set_rgb(i, 255, 0, 200)
+            elif i // 8 == 2:
+                # violet
+                leds.set_rgb(i, 153, 50, 204)
+            elif i // 8 == 3:
+                # cyan
+                leds.set_rgb(i, 0, 255, 255)
+            elif i // 8 == 4:
+                # green
+                leds.set_rgb(i, 0, 255, 0)   
+        
+
+        leds.update()
+
+    def nextImage(self, ctx: Context):
+        path = f"/flash/sys/apps/chubb/cbimage{str(self.picidx)}_240.png"
+        self.picidx = self.picidx + 1
+        if self.picidx > 11:
+           self.picidx = 0
+        return path
+
+    def think(self, ins: InputState, delta_ms: int) -> None:
+        super().think(ins, delta_ms) # Let Application do its thing
+
+
+if __name__ == '__main__':
+    st3m.run.run_view(NyanCat(ApplicationContext()))
diff --git a/cbimage0_240.png b/cbimage0_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..90937c0517650af6a0a4eeb192c373e20986bc54
Binary files /dev/null and b/cbimage0_240.png differ
diff --git a/cbimage10_240.png b/cbimage10_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..98ff0b9cd0ce6129fa67d66927731696729aaea3
Binary files /dev/null and b/cbimage10_240.png differ
diff --git a/cbimage11_240.png b/cbimage11_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..2551536a01e8043a87b82813b67e434663b6e661
Binary files /dev/null and b/cbimage11_240.png differ
diff --git a/cbimage1_240.png b/cbimage1_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..9addcee64c4b7d86404ebbe71c4d48cd681e6dfe
Binary files /dev/null and b/cbimage1_240.png differ
diff --git a/cbimage2_240.png b/cbimage2_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..53aa32d0437736c51f5c55afe2f6c0ea91bd68e7
Binary files /dev/null and b/cbimage2_240.png differ
diff --git a/cbimage3_240.png b/cbimage3_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..849b8e68d08162d15a1cff4439f7194150d95d36
Binary files /dev/null and b/cbimage3_240.png differ
diff --git a/cbimage4_240.png b/cbimage4_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..35bcbef9c0833a90e55507ef179951a8c54f4b14
Binary files /dev/null and b/cbimage4_240.png differ
diff --git a/cbimage5_240.png b/cbimage5_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..062d6f716e57e943c3c6fa7ce8b499335eb57657
Binary files /dev/null and b/cbimage5_240.png differ
diff --git a/cbimage6_240.png b/cbimage6_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..fc367bfb318b2553fe0dbe2533affe8bfb5fb746
Binary files /dev/null and b/cbimage6_240.png differ
diff --git a/cbimage7_240.png b/cbimage7_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..703b86b4eeef7801bf6cb3705bf6b5fa63256042
Binary files /dev/null and b/cbimage7_240.png differ
diff --git a/cbimage8_240.png b/cbimage8_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..a980d8a44e1226370061d52811245e1d54cd762e
Binary files /dev/null and b/cbimage8_240.png differ
diff --git a/cbimage9_240.png b/cbimage9_240.png
new file mode 100644
index 0000000000000000000000000000000000000000..3861e0bf70443f13675630bc704ef5025720e591
Binary files /dev/null and b/cbimage9_240.png differ
diff --git a/flow3r.toml b/flow3r.toml
new file mode 100644
index 0000000000000000000000000000000000000000..43f5c32e8d7a5e2ad25c287b5f9625b071a971fa
--- /dev/null
+++ b/flow3r.toml
@@ -0,0 +1,13 @@
+[app]
+name = "nyancat"
+menu = "Badge"
+
+[entry]
+class = "NyanCat"
+
+[metadata]
+author = "chubb"
+license = "matewarelicese"
+url = "https://git.flow3r.garden/chubb/nyan-cat"
+description = "nyan cat - yay"
+version = 1