gliechtenstein

23 ms·

1. 61.▲
   by gliechtenstein 10y ago

   Interesting, I haven't thought of that idea. I'll make a note so when we get to it we'll make sure to look into the option. Thank you so much for the advice!
2. 62.▲
   by gliechtenstein 10y ago

   Thank you for noticing! :)
3. 63.▲
   by gliechtenstein 10y ago

   Thank you! I think this thread is relevant: https://news.ycombinator.com/item?id=12879487
4. 64.▲
   by gliechtenstein 10y ago

   Thanks! I think the best way to see is to actually jump in and try it out. I tried my best to make the onboarding as seamless as possible, so normally it should take like 20 seconds from download to having the app on your phone (assuming yo
5. 65.▲
   by gliechtenstein 10y ago

   I think I need to make some changes to the main screenshots, those are actually one of the most advanced features of Jasonette. You don't really need to use those templates at all. What those templates do is let you do advanced stuff l
6. 66.▲
   by gliechtenstein 10y ago

   Yup, try this https://jasonbase.com/things/zn1/edit
7. 67.▲
   by gliechtenstein 10y ago

   nope!
8. 68.▲
   by gliechtenstein 10y ago

   Yup I worked on open sourcing it for 6 months! This is the open source version of Jasonclient
9. 69.▲
   by gliechtenstein 10y ago

   Thank you for the advice! Honestly it means a lot!
10. 70.▲
    by gliechtenstein 10y ago

    I totally understand where you're coming from. Here's my rationale: Most mobile devices and future devices will already use JSON as main method of data transmission. And I'm trying to build something that's optimized for
11. 71.▲
    by gliechtenstein 10y ago

    Currently, it is possible to set a data-uri as the root url (in a correct format https://en.wikipedia.org/wiki/Data_URI_scheme ) I think that's one way you could handle this situation. Or one could fork the code an
12. 72.▲
    by gliechtenstein 10y ago

    Thanks for the article. I am sorry to hear what happened to your project, but I think, in my case because I didn't build this from scratch, but it was extracted out from an existing app, I was able to get this to a point where I'm
13. 73.▲
    by gliechtenstein 10y ago

    Almost correct. To be precise, it doesn't have the objects in memory, it instantiates all the native components on demand based on the JSON recipe. And all of them of course go away once you close that view.
14. 74.▲
    by gliechtenstein 10y ago

    Thanks for the feedback! We discuss that issue here: https://github.com/Jasonette/JASONETTE-iOS/issues/4 Please follow the project if you're interested in finding out where this goes :)
15. 75.▲
    by gliechtenstein 10y ago

    There's an issue thread where we're discussing this: https://github.com/Jasonette/JASONETTE-iOS/issues/4
16. 76.▲
    by gliechtenstein 10y ago

    Yup that's what I meant by API versioning. Instead of having to deploy the physical app to the appstore, you are deploying your API, since basically you're building your native app on the server.
17. 77.▲
    by gliechtenstein 10y ago

    No that's me. I'm Ethan, and I created that Ethan app. Jasonette was born out of my frustration with various aspects of working on the Ethan app. So that app (and all other apps I have created since) currently run on Jasonette. So
18. 78.▲
    by gliechtenstein 10y ago

    > you could add scripting I did: https://jasonette.github.io/documentation/actions/
19. 79.▲
    by gliechtenstein 10y ago

    https://jasonette.github.io/documentation/actions/
20. 80.▲
    by gliechtenstein 10y ago

    Why would you want to have a version of your app? I think one of the coolest part is it works like a website but natively. If you wanted to version apps, I think you could version it at git level, or just think of it as an API deployment. N
21. 81.▲
    by gliechtenstein 10y ago

    No worries, why don't we just add HJSON support!
22. 82.▲
    by gliechtenstein 10y ago

    Yup, in fact this was extracted from production apps on the appstore. Here's one: www.textethan.com The way this works is like how a web browser works, all the code you will ever need is already in the binary, the JSON markup is just u
23. 83.▲
    by gliechtenstein 10y ago

    Thank you! I had no idea documentation would be this hard. As a wise man said, I learned that open source project is "1% inspiration and 99% documentation" :)
24. 84.▲
    by gliechtenstein 10y ago

    There's a $cache action where you can store any JSON object into cache associated with the current url and reuse it later https://jasonette.github.io/documentation/actions/#cache-vs-... Also there's an u
25. 85.▲
    by gliechtenstein 10y ago

    Guys, the author here. This is my first open source project and I worked really hard on it for 5 months. I think it's really cool, and I hope you guys like it. I would appreciate any kind of feedback!
26. 86.▲
    Show HN: Make an app by adding JSON to this app(github.com)

    648 points by gliechtenstein 10y ago|176 comments
27. 87.▲
    by gliechtenstein 10y ago

    I agree with native apps not being useful for many cases. However I don't think that means the old web is the future. It is true that companies like Patagonia don't need a native app. In fact, most native apps from large media com
28. 88.▲
    by gliechtenstein 10y ago

    Hi, Jason is still on the appstore. There is absolutely no problem in that department since the approach is far from violating any Apple policy (it works just like a browser and doesn't "download" any additional code). Soon a
29. 89.▲
    Show HN: Jasonette – Send entire native mobile app over HTTP as JSON(jasonette.com)

    8 points by gliechtenstein 10y ago|3 comments
30. 90.▲
    by gliechtenstein 10y ago

    I think you're looking for this http://www.jasonclient.org/doc/#template-reference you can use javascript expressions inside templates so everything you mentioned is possible using javascript. Here's an examp