This document discusses a discovery commerce platform that aggregates fashion product sales. It uses Titanium for rapid development of Android and web applications. The platform focuses on discovering customer needs through experiments and analytics rather than perfecting the development process. Titanium allows writing code once that runs on multiple platforms but has some limitations around performance and native capabilities.

1. Hello!
I’m not a developer but I do programms.
Rodion Mamin, Spycob

2. We are an aggregator or fashion product sales over 50%
It’s discovery commerce platform like Pinterest but for
sales
Who we are.

3. Customer Development &
Lean Startup

4. Our principles
● Do as fast as possible, one month for a week.
● Often when you develop software you spend much
more time than your expected
● In startup time is the most valuable product
● Do not try to solve the problem “right” - do it as
fast as you can. (But do not forget to make it
possible to upgrade your “fast result” to “right”
● Use tests and the only God is Analytics

5. Our stack
- Android first
- .NET scrapper
- jQuery/PHP site
- Localytics/Google Analytics
- NodeJS for trigger emails,

6. Why we use Titanium
- We prefer to focus on product and discover what
our user need not on development.
- 3-4 minor updates a week with 1 major
- if you’ll try to do the best and as it should be
you’ll spend much more time time to make a
release

7. Titanium Architecture

8. Alloy
● XML for markup as HTML
● TSS for styling as CSS
● JS for business logic

9. Native modules
- Email from Google Account
- Google Analytics
- Two-columns ListView

10. Experiments for the past
3 month
1. Design
2. Changed a lot of texts
3. Push notifications
4. Referral system -> promo codes
5. Lot of people were trying to search brands,
“gender search” -> done.
6. Subscription -> people thought it’s filter ->
changed the design -> people do not need it.

11. Titanium pros and contras
● rapid development
● write once run everywhere
● no need to learn native
● share code between app
and server
● lot of community modules
● slow platform-specific updates
● single-threaded
● lot of problems with TableViews
● Poor basic access to native abilities
● problem with modules

12. Example

13. Questions?
Facebook, LinkedIn, Google - Rodion Mamin