6 ms·
Really great stuff! What is the most advanced application you have created with this? What functionality do you think is still lacking? If you were to try to
by mentos 10y ago
Really great stuff!
What is the most advanced application you have created with this? What functionality do you think is still lacking?
If you were to try to create a full featured app I imagine you'd find that working in Swift is the better option.
What this reveals to me is that the App Store submission and update process is so time consuming you would rather write your logic in Json than in native Swift/ObjC.
If Xcode let you instantaneously push app binary updates would this be as useful?
- gliechtenstein 10y agoThere's an issue thread where we're discussing this: https://github.com/Jasonette/JASONETTE-iOS/issues/4 https://github.com/Jasonette/JASONETTE-iOS/issues/4
- mentos 10y agoMy fear is that for most apps Jasonette will be too abstract and require lower level languages like Swift/ObjC to be more expressive. I think a good exercise would be to find a popular mobile app and recreate all of the functionality with Jasonette, developing missing features where you need them. A demo showing you recreate Tinder or iMessage by bolting a few pieces of logic together in Jasonette would go a long way in maturing the functionality and demonstrating its viability. Have you considered weaving Parse or Firebase into this?
- gliechtenstein 10y agoYup, try this https://jasonbase.com/things/zn1/edit https://jasonbase.com/things/zn1/edit
- mentos 10y agoThe advantages of creating your own wysiwyg editor is that you can control exactly what functionality Jasonette supports and allow developers to create views across different platforms (right now Xcode is Mac only). But have you considered starting with Interface Builder and creating a tool to convert IB views to JSON? Interface Builder is home to a lot of developers who already understand how to use that tool, asking devs to work in a new half baked editor would probably be frustrating and add more complexity/moving parts which is your enemy as a new project/endeavor. If you create a tool that just converts IB views to JSON you can demonstrate progress much faster and learn and experiment with what the requirements of the final editor are. It will be much easier to stand up and way less effort than maintaining your own editor codebase while the project is young. Your time is the most valuable thing you have so don't spend it creating a new editor which could be its own project in itself. You want to put it towards expanding missing functionality between JSON and native components. One day when you find success and if you really still need to limit the user you can move all the functions you made for converting Interface Builder views into your own custom editor. I think first thing I would do is take a very complicated interface view from a native project and analyze the view hierarchy and report errors to the user like "Warning: Nested UITableViews are not supported in Jasonette", "UIButton delegate will be ignored", etc. Then once you create this sort of 'unit test' that the IB is well-formatted you can then go about exporting it to JSON. There may be a world where you actually are able to use all of the functionality of IB and don't ever have to have your own editor.
- gliechtenstein 10y agoInteresting, 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!
- leereeves 10y agoHow is Apple going to react when you change the JSON (and thus the app, as seen by the user) without getting approval for the changes?
- beyti 10y agoIf you are showing a web page inside your app and the web page contents changed, is that a problem too? I mean where's the line defined by apple for the term "change".
- leereeves 10y agoApple only allows the iOS WebKit framework, so in a way, all apps that show webpages are simply wrappers around an Apple browser. So I wouldn't be surprised if they react to that differently.
- Animats 10y agoWill Apple eject this app from their web store for downloading code? Maybe not. Current Apple policy: 2.5.2 Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code, including other iOS, watchOS, Mac OS X, or tvOS apps. Older policy: 3.3.2 — An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise. No interpreted code may be downloaded or used in an Application except for code that is interpreted and run by Apple’s Documented APIs and built-in interpreter(s). Apple once prohibited a Commodore 64 emulator because it had a BASIC intepreter. But they've lightened up a bit.