@@ -754,12 +754,61 @@ class="mx-auto flex w-full max-w-2xl flex-col items-center gap-4 pt-10"
754
754
</p >
755
755
</x-faq-card >
756
756
757
- <x-faq-card question =" When will Android support be ready?" >
758
- <p >It's READY! Sign up and build apps for Android today!</p >
757
+ <x-faq-card
758
+ question =" What does 'build unlimited apps, release X production apps' mean?"
759
+ >
760
+ <p >
761
+ Every NativePHP for Mobile license entitles you to
762
+ <i >release</i > a certain number of applications.
763
+ A 'released' app is when it's published or distributed
764
+ (typically through an app store).
765
+ </p >
766
+ <br />
767
+ <p >
768
+ However, you are welcome to
769
+ <i >build</i >
770
+ (develop), as many apps as you want. If no one else besides you
771
+ and other license holders have access to your app, then it
772
+ doesn't count towards your quota of 'released' apps.
773
+ </p >
774
+ </x-faq-card >
775
+
776
+ <x-faq-card question =" What is a 'developer seat'?" >
777
+ <p >
778
+ A 'developer seat' represents an individual developer that
779
+ can build apps under that license plan.
780
+ </p >
781
+ <br />
782
+ <p >
783
+ For example, on the Pro plan, the license holder can create up to 10 unique
784
+ license keys that can be assigned to individual developers,
785
+ one key per developer.
786
+ </p >
787
+ <br />
788
+ <p >
789
+ This allows the license holder to control who has the ability to
790
+ use their license for building apps. You can add or remove developers
791
+ and each will get their own unique license key. If a developer leaves
792
+ your team, you can revoke their license key to prevent abuse.
793
+ </p >
759
794
</x-faq-card >
760
795
761
- <x-faq-card question =" When will the EAP end?" >
762
- <p >The EAP will end May 31, 2025.</p >
796
+ <x-faq-card
797
+ question =" Is it possible to purchase additional developer seats or released apps?"
798
+ >
799
+ <p >
800
+ You can purchase more Mini or Pro licenses as needed.
801
+ </p >
802
+ </x-faq-card >
803
+
804
+ <x-faq-card question =" What was the EAP and when did it end?" >
805
+ <p >
806
+ The Early Access Program (EAP) provided initial access to
807
+ the NativePHP for Mobile platform for early adopters at
808
+ reduced pricing while we worked on releasing v1 of the
809
+ technology. The EAP started in February and ended in May
810
+ 2025.
811
+ </p >
763
812
</x-faq-card >
764
813
765
814
<x-faq-card question =" Which price will my license renew at?" >
@@ -784,6 +833,7 @@ class="mx-auto flex w-full max-w-2xl flex-col items-center gap-4 pt-10"
784
833
<x-faq-card question =" Can I upgrade or downgrade my license later?" >
785
834
<p >That's not currently possible.</p >
786
835
</x-faq-card >
836
+
787
837
<x-faq-card question =" Will my apps built with NativePHP be secure?" >
788
838
<p >
789
839
Definitely. NativePHP for Mobile apps are just like other
@@ -801,6 +851,7 @@ class="mx-auto flex w-full max-w-2xl flex-col items-center gap-4 pt-10"
801
851
build!
802
852
</p >
803
853
</x-faq-card >
854
+
804
855
<x-faq-card question =" Can I get an invoice?" >
805
856
<p >
806
857
If you purchased after May 6, 2025, you should get an
@@ -835,87 +886,4 @@ class="inline-block underline hover:text-violet-400"
835
886
</x-faq-card >
836
887
</div >
837
888
</section >
838
-
839
- {{-- Why Join Program Section --}}
840
- <section
841
- class =" mx-auto mt-20 max-w-5xl px-5"
842
- aria-labelledby =" join-program-heading"
843
- >
844
- <article
845
- x-init ="
846
- () => {
847
- motion.inView(
848
- $el,
849
- (element) => {
850
- motion.animate(
851
- $el,
852
- {
853
- opacity: [0, 1],
854
- x: [-10, 0],
855
- },
856
- {
857
- duration: 0.7,
858
- ease: motion.easeOut,
859
- },
860
- )
861
- },
862
- {
863
- amount: 0.2,
864
- },
865
- )
866
- }
867
- "
868
- class =" prose mx-auto max-w-2xl opacity-0 dark:text-gray-400"
869
- >
870
- <h2
871
- id =" join-program-heading"
872
- class =" dark:text-white"
873
- >
874
- Why Join the Early Access Program?
875
- </h2 >
876
- <p >
877
- From the beginning, NativePHP has been focused on Windows, Mac,
878
- and Linux. Until now!
879
- </p >
880
- <p >
881
- We believe that breaking the mobile frontier is what makes this
882
- project truly compelling... and truly cross-platform.
883
- </p >
884
- <p >
885
- With
886
- <strong class =" dark:text-white" >NativePHP for Mobile</strong >
887
- , we are excited about the possibilities that lie ahead.
888
- </p >
889
- <p >
890
- However, to make this vision a reality for both iOS and Android,
891
- we need your support.
892
- </p >
893
- <p >
894
- As an EAP member, you will be supporting the continued
895
- development of all of NativePHP, but especially of NativePHP for
896
- mobile.
897
- </p >
898
- <p >
899
- You'll have the opportunity to influence the direction of the
900
- project and provide critical feedback right from an early stage.
901
- </p >
902
- <p >
903
- You'll get exclusive access to all the latest features first and
904
- special perks for the life of the NativePHP project... a project
905
- we plan to be working on for a long time to come!
906
- </p >
907
- <p >
908
- Please join us on this exciting journey to expand NativePHP onto
909
- mobile platforms.
910
- </p >
911
- <p class =" italic" >We can't wait to see what you build!</p >
912
- <p >
913
- <span class =" font-bold italic dark:text-white" >
914
- Simon & ; Shane
915
- </span >
916
- <br />
917
- <span class =" text-indigo-400" >Creators of NativePHP</span >
918
- </p >
919
- </article >
920
- </section >
921
889
</x-layout >
0 commit comments